From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sam Ruby <rubys@intertwingly.net>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
x86@kernel.org
Subject: Re: [APIC] Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8
Date: Mon, 9 Feb 2009 21:31:09 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.1.10.0902092129050.12457@ftp.linux-mips.org> (raw)
In-Reply-To: <20090203114849.b661f1ce.akpm@linux-foundation.org>
On Tue, 3 Feb 2009, Andrew Morton wrote:
> > >> [ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> > >> [ 0.296001] 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.
> > >> [ 0.296001]
> > >>
> > >> Able to get past this issue using "noapic", at which point things mostly
> > >> work,
> > >
> > > Join the ever-growing noapic club :(
> > >
> > > I assume this is an ACPI problem. Or at least, a BIOS problem which
> > > ACPI can solve for us.
> >
> > My understanding is that APCI and APIC are two different things.
>
> They sure are. But it is ACPI which communicates with the BIOS to tell
> the kernel about the APIC, hwo it's wired up, etc.
>
> Although in this case it looks like the problem might be with the
> mp-bios tables, which ACPI does not handle. In which case it would be
> core x86 code which will have to fix this up, not ACPI.
The message is misleading. It predates the ACPI and has never been
updated. It applies equally to both MPS and ACPI systems. Earlier
bootstrap messages can be used to determine which configuration method has
been used by the kernel on this system (many systems provide both).
Maciej
prev parent reply other threads:[~2009-02-09 21:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4978767D.4060700@intertwingly.net>
2009-01-30 8:07 ` [APIC] Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8 Andrew Morton
2009-02-03 17:55 ` Sam Ruby
2009-02-03 17:58 ` Sam Ruby
2009-02-03 19:48 ` Andrew Morton
2009-02-03 20:19 ` Sam Ruby
2009-02-03 21:03 ` Thomas Gleixner
2009-02-04 3:28 ` Sam Ruby
2009-02-04 4:42 ` Len Brown
2009-02-09 23:50 ` Sam Ruby
2009-02-10 2:10 ` yakui_zhao
2009-02-10 11:46 ` Sam Ruby
2009-02-11 1:42 ` yakui_zhao
2009-02-11 2:06 ` Sam Ruby
2009-02-11 19:26 ` Sam Ruby
2009-02-04 4:35 ` Len Brown
2009-02-09 21:31 ` Maciej W. Rozycki [this message]
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=alpine.LFD.1.10.0902092129050.12457@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubys@intertwingly.net \
--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