From: Andrew Morton <akpm@osdl.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: herbert@gondor.apana.org.au, len.brown@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [APIC] Avoid change apic_id failure panic
Date: Thu, 3 Jun 2004 16:44:15 -0700 [thread overview]
Message-ID: <20040603164415.06a7098c.akpm@osdl.org> (raw)
In-Reply-To: <20040603233748.GN21007@holomorphy.com>
William Lee Irwin III <wli@holomorphy.com> wrote:
>
> Herbert Xu <herbert@gondor.apana.org.au> wrote:
> >> I've received two reports at http://bugs.debian.org/251207 where
> >> ioapic caused machines to lock up during booting due to the
> >> change apic_id panic in arch/i386/kernel/io_apic.c.
> >> Since it appears that we can avoid panicking at all, I think we
> >> should replace the panic calls with the following patch which
> >> attempts to continue after the failure.
> >> I've also done the same thing to the other panic() call in the
> >> same function.
>
> On Thu, Jun 03, 2004 at 04:20:45PM -0700, Andrew Morton wrote:
> > Well. Question is, why are we getting insame APIC ID's in there in the
> > first place?
>
> They're usually not insane. xAPIC's have 8-bit physical ID's, not 4-bit,
> but no one's bothered tracking whether the APIC's found were serial APIC
> or xAPIC, and then dispatching on that in the IO-APIC physid check to
> avoid unnecessarily renumbering the things or panicking.
So... what should we do?
next prev parent reply other threads:[~2004-06-03 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 10:13 Herbert Xu
2004-06-03 23:20 ` Andrew Morton
2004-06-03 23:37 ` William Lee Irwin III
2004-06-03 23:44 ` Andrew Morton [this message]
2004-06-03 23:48 ` William Lee Irwin III
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=20040603164415.06a7098c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=herbert@gondor.apana.org.au \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®