linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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!
Date: Mon, 27 Jul 2020 22:51:16 +0200	[thread overview]
Message-ID: <87h7tsbs1n.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <18cb4d48-6571-1fdb-5902-ba64c23eee75@broadcom.com>

Scott,

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

Also you might check whether there are BIOS updates for this board. The
early Ryzen BIOSes had some rough edges.

Thanks,

        tglx


  parent reply	other threads:[~2020-07-27 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 18:39 Kernel panic - not syncing: IO-APIC + timer doesn't work! Scott Branden
2020-07-27 19:46 ` Andy Shevchenko
2020-07-27 20:51 ` Thomas Gleixner [this message]
2020-07-27 21:06   ` Scott Branden
2020-07-27 22:48   ` Scott Branden
2020-07-28  8:22     ` Thomas Gleixner
2020-07-28 17:30       ` Scott Branden
2020-07-29  9:50         ` Thomas Gleixner
2020-07-29 18:29           ` Tom Lendacky
2020-07-29 23:28             ` Scott Branden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7tsbs1n.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=scott.branden@broadcom.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).