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: <959f82d7-2a3a-44a3-5781-42f68c8632b6@broadcom.com>
Date:   Mon, 27 Jul 2020 14:06:44 -0700
From:   Scott Branden <scott.branden@...adcom.com>
To:     Thomas Gleixner <tglx@...utronix.de>, 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!

Hi Thomas,


On 2020-07-27 1:51 p.m., Thomas Gleixner wrote:
> Scott,
>
> Scott Branden <scott.branden@...adcom.com> writes:
>
>> Occasionally I get the following Kernel panic on boot.  This is
>> running on the latest kernel but have seen it previously as well.
>> "Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with
>> apic=debug and send a report."
>>
>> I don't know who I am support to send a report to.  But here is the log with apic=debug
>> [    0.006000] ENABLING IO-APIC IRQs
>> [    0.007000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
>> [    0.007000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
>> [    0.007000] ...trying to set up timer (IRQ0) through the 8259A ...
>> [    0.007000] ..... (found apic 0 pin 2) ...
>> [    0.007000] ....... failed.
>> [    0.007000] ...trying to set up timer as Virtual Wire IRQ...
>> [    0.007000] ..... failed.
>> [    0.007000] ...trying to set up timer as ExtINT IRQ...
>> [    0.007000] ..... failed :(.
>> [    0.007000] Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the 'noapic' option.
> Nothing which rings a bell. Can you please provide a boot log from a
> successful boot with apic=debug on the command line?
boot log attached.
>
> Also you might check whether there are BIOS updates for this board. The
> early Ryzen BIOSes had some rough edges.
Will get someone to check for updates.
It's a remote system so don't have direct access to the EFI Shell right now.
>
> Thanks,
>
>         tglx
>
Thanks,
Scott

View attachment "apicdebug.txt" of type "text/plain" (110154 bytes)