Hi Thomas,

On 2020-07-28 1:22 a.m., Thomas Gleixner wrote:
> Scott,
>
> Scott Branden <scott.branden@broadcom.com> writes:
>> Bios now updated to latest.  Same kernel panic issue.  Log below.
>>
>> 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?
So far I have only been able to reproduce the issue by cold start with power off for only a few seconds
before re-powering the system.  It has not failed via reboot yet that I remember.
Will have to keep my eye on whether using reboot is an issue or not.
And also keeping power off longer when doing a cold start.
>
>> [    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
>> [    0.000000] Command line: BOOT_IMAGE=/bzImage ima_policy=tcb
>> apic=debug ip=dhcp raid=noautodetect console=ttyS0,115200
>> root=/dev/nfs nfsroot=192.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.
Please find attached the failed console log with ignore_loglevel.
>
> Thanks,
>
>         tglx
Regards,
Scott