public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ingo Oeser <ioe-lkml@rameria.de>,
	Andi Kleen <andi@firstfloor.org>,
	Chuck Ebbert <cebbert@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why do so many machines need "noapic"?
Date: Mon, 24 Sep 2007 17:32:24 -0400	[thread overview]
Message-ID: <20070924213224.GI8127@redhat.com> (raw)
In-Reply-To: <20070915120824.GA21243@srcf.ucam.org>

On Sat, Sep 15, 2007 at 01:08:25PM +0100, Matthew Garrett wrote:
 > On Sat, Sep 15, 2007 at 04:08:02AM -0700, Andrew Morton wrote:
 > 
 > > I believe that about two years ago we broke something which caused quite a
 > > large number of people to need noapic.  Is that the case with any of your
 > > machines?  Do you know if they run 2.6.ancient without noapic?
 > 
 > My recollection is that we shifted from "Enable the apic even if the 
 > BIOS disabled it" to "Only use the apic if the BIOS didn't disable it" 
 > around that time, which meant that distributions could actually turn on 
 > apic-on-up support without breaking everything. That might correspond to 
 > what you're seeing.

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 ?

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-09-24 21:32 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 [this message]
2007-09-27 22:03             ` Phillip Susi
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=20070924213224.GI8127@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=cebbert@redhat.com \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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