From: Phillip Susi <psusi@cfl.rr.com>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why do so many machines need "noapic"?
Date: Thu, 27 Sep 2007 18:03:16 -0400 [thread overview]
Message-ID: <46FC28A4.9080008@cfl.rr.com> (raw)
In-Reply-To: <20070924213224.GI8127@redhat.com>
Dave Jones wrote:
> If memory serves correctly, that was circa 2.6.10, back in these commits..
>
> commit a068ea13d1db406e15c346e93530343f6e70184c
> Author: Len Brown <len.brown@intel.com>
> Date: Sun Oct 10 05:21:08 2004 -0400
>
> [ACPI] If BIOS disabled the LAPIC, believe it by default.
> "lapic" is available to force enabling the LAPIC
> in the event you know more than your BIOS vendor.
> http://bugzilla.kernel.org/show_bug.cgi?id=3238
>
> commit 2fcfece90db9643b6f30a7ad343898a2871e6a81
> Author: Len Brown <len.brown@intel.com>
> Date: Sat Oct 9 20:12:45 2004 -0400
>
> [ACPI] Don't enable LAPIC when the BIOS disabled it.
> Doing so apparently breaks every Dell on Earth.
> http://bugzilla.kernel.org/show_bug.cgi?id=3238
>
>
> But those changes relate to the local APIC, which 'noapic' shouldn't
> have any effect on should it ?
If the LAPIC is disabled, then you CAN'T use the IO-APIC right? So then
wouldn't the noapic option have no effects since the apic is already
disabled?
next prev parent reply other threads:[~2007-09-27 22:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 23:30 Why do so many machines need "noapic"? Chuck Ebbert
2007-09-06 11:31 ` Andi Kleen
2007-09-07 19:34 ` Chuck Ebbert
2007-09-08 5:17 ` Prakash Punnoor
2007-09-10 19:12 ` Chuck Ebbert
2007-09-10 19:44 ` Andi Kleen
2007-09-10 23:33 ` Chuck Ebbert
2007-09-13 16:38 ` Chuck Ebbert
2007-09-25 9:06 ` Thomas Gleixner
2007-09-15 7:39 ` Andrew Morton
2007-09-15 10:58 ` Ingo Oeser
2007-09-15 11:08 ` Andrew Morton
2007-09-15 12:08 ` Matthew Garrett
2007-09-24 21:32 ` Dave Jones
2007-09-27 22:03 ` Phillip Susi [this message]
2007-09-15 18:42 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2007-09-08 4:12 Al Boldi
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=46FC28A4.9080008@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-kernel@vger.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