From: Mikael Pettersson <mikpe@csd.uu.se>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"mobil@wodkahexe.de" <mobil@wodkahexe.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc4 No local APIC present or hardware disabled
Date: Mon, 25 Oct 2004 16:08:58 +0200 [thread overview]
Message-ID: <16765.2298.953135.524930@alkaid.it.uu.se> (raw)
In-Reply-To: <Pine.LNX.4.58L.0410241615350.14448@blysk.ds.pg.gda.pl>
Maciej W. Rozycki writes:
> > I agree with Alan that accusing the BIOS of being buggy is unwarranted.
>
> I disagree. If the firmware performs any actions on hardware without
> asking the OS for permission, it *must* be prepared for it to be in any
> possible state and handle it correctly, including any transitional states
> (as it does respect spinlocks). Otherwise it's buggy.
But in this case the BIOS explicitly disabled the local APIC. It may
have a legitimate reason for doing so (e.g. old #SMM code), so if the
Linux kernel overrides that disablement and things break, it really is
the kernel's fault not the BIOS'.
> patch-2.6.9-lapic-7
I'm Ok with this patch.
/Mikael
next prev parent reply other threads:[~2004-10-25 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 17:54 2.6.9-rc4 No local APIC present or hardware disabled mobil
2004-10-12 16:11 ` Mikael Pettersson
2004-10-12 16:15 ` Prakash K. Cheemplavam
2004-10-13 23:59 ` Maciej W. Rozycki
2004-10-14 10:52 ` Mikael Pettersson
2004-10-14 22:27 ` Maciej W. Rozycki
2004-10-15 12:26 ` Alan Cox
2004-10-15 13:53 ` Mikael Pettersson
2004-10-24 15:44 ` Maciej W. Rozycki
2004-10-24 15:11 ` Alan Cox
2004-10-25 14:08 ` Mikael Pettersson [this message]
2004-10-14 11:59 ` mobil
2004-10-14 21:25 ` Maciej W. Rozycki
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=16765.2298.953135.524930@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mobil@wodkahexe.de \
/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