linux-kernel - Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87blk0aw1k.fsf@nanos.tec.linutronix.de>
Date:   Tue, 28 Jul 2020 10:22:31 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Scott Branden <scott.branden@...adcom.com>, bp@...en8.de,
        x86@...nel.org, mingo@...hat.com
Cc:     linux-kernel@...r.kernel.org
Subject: Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!

Scott,

Scott Branden <scott.branden@...adcom.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?

> [    0.000000] Linux version 5.8.0-rc6 (oe-user@...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.

Thanks,

        tglx