Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Scott Branden <scott.branden@broadcom.com>, bp@alien8.de,
        x86@kernel.org, mingo@redhat.com
Cc:     linux-kernel@vger.kernel.org
Subject: Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!
In-Reply-To: <e0ce41cd-9149-e43e-f4ca-e75503cb82e3@broadcom.com>
References: <18cb4d48-6571-1fdb-5902-ba64c23eee75@broadcom.com> <87h7tsbs1n.fsf@nanos.tec.linutronix.de> <e0ce41cd-9149-e43e-f4ca-e75503cb82e3@broadcom.com>
Date:   Tue, 28 Jul 2020 10:22:31 +0200
Message-ID: <87blk0aw1k.fsf@nanos.tec.linutronix.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Scott,

Scott Branden <scott.branden@broadcom.com> writes:
> Bios now updated to latest.=C2=A0 Same kernel panic issue.=C2=A0 Log belo=
w.
>
> I think it is related to power cycling quickly.
> Should APIC work if PC power cycled in a few seconds or is that the
> problem?

Yes, emphasis on should. Just to clarify, if you reboot it works and
cold start works as well if power was off long enough?

> [=C2=A0=C2=A0=C2=A0 0.000000] Linux version 5.8.0-rc6 (oe-user@oe-host) (=
x86_64-poky-linux-gcc (GCC) 10.1.0, GNU ld (GNU Binutils) 2.34.0.20200220) =
#1 SMP Sat Jul 25 03:55:25 UTC 2020
> [=C2=A0=C2=A0=C2=A0 0.000000] Command line: BOOT_IMAGE=3D/bzImage ima_pol=
icy=3Dtcb
> apic=3Ddebug ip=3Ddhcp raid=3Dnoautodetect console=3DttyS0,115200
> root=3D/dev/nfs nfsroot=3D192.168.1.100:/nfs/vxc,hard,tcp,intr,v3 rootwait
> nfsrootdebug

The working dmesg and the failing console log are hard to compare
because the latter does not contain debug level printks. Please add
'ignore_loglevel' to the command line parameters.

Thanks,

        tglx