From: Fengguang Wu <fengguang.wu@intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: 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.
Date: Mon, 3 Jun 2013 19:26:24 +0800 [thread overview]
Message-ID: <20130603112624.GA7623@localhost> (raw)
In-Reply-To: <51AC7B2C.5000204@intel.com>
On Mon, Jun 03, 2013 at 01:17:00PM +0200, Rafael J. Wysocki wrote:
> On 6/2/2013 6:20 AM, Fengguang Wu wrote:
> >Greetings,
> >
> >FYI, I got this occasionally in some of my machines when testing the
> >pm/bleeding-edge branch:
> >
> >[ 0.040000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> >[ 0.044000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> >[ 0.044000] ...trying to set up timer (IRQ0) through the 8259A ...
> >[ 0.044000] ..... (found apic 0 pin 2) ...
> >[ 0.048000] ....... failed.
> >[ 0.048000] ...trying to set up timer as Virtual Wire IRQ...
> >[ 0.048000] ..... failed.
> >[ 0.048000] ...trying to set up timer as ExtINT IRQ...
> >[ 0.052000] ..... failed :(.
> >[ 0.052000] 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.
> >
> >Bisect result is unfortunately not reliable..
>
> Can you please check if this is reproducible with the acpi-hotplug
> branch alone?
Nope, it also shows up in upstream kernel. Sorry.. I'll try more bisect.
Thanks,
Fengguang
next prev parent reply other threads:[~2013-06-03 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130602042033.GB16050@localhost>
2013-06-03 11:17 ` 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 Rafael J. Wysocki
2013-06-03 11:26 ` Fengguang Wu [this message]
2013-06-04 0:43 ` Fengguang Wu
2013-06-04 0:52 ` Rafael J. Wysocki
2013-06-04 9:13 ` Martin Mokrejs
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=20130603112624.GA7623@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.