public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] Re: [BKPATCH] LAPIC fix for 2.6
Date: Mon, 11 Oct 2004 13:42:11 +0200	[thread overview]
Message-ID: <20041011114211.GF14615@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0410101744110.3897@ppc970.osdl.org>

On Sun, Oct 10, 2004 at 05:47:05PM -0700, Linus Torvalds wrote:
> 
> 
> On Sun, 10 Oct 2004, Maciej W. Rozycki wrote:
> > 
> >  Hmm, any particular reason to keep the local APIC disabled by default?  
> 
> Yes. It changes interrupt handling, so any SMM stuff tends to break on
> BIOSes that don't know about APICs. Things like the magic keys etc. It
> apparently also breaks some ACPI stuff (likely AML code that "knows" that
> interrupts are done with the legacy controller).
> 
> Mostly a laptop issue, I suspect - simply because desktops don't do 
> anything strange these days.

It's more than a laptop issue. Especially older desktops still don't
work with APIC by default, and even a lot of modern ones have problems.  

It works around ACPI bugs. Some common issues I ran into on x86-64:
nvidia nforce2/3 is still often broken because of the bogus timer override 
so many BIOS have) 
Some VIA K8 boards get mysterious IDE DMA errors after some time when the APIC 
is on.

[Patch for the Nvidia thing is pending - just always ignore it - but not 
submitted yet for i386 yet. x86-64 has it fixed in -mm*]

-Andi

      reply	other threads:[~2004-10-11 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 17:35 [BKPATCH] LAPIC fix for 2.6 Len Brown
2004-10-10 17:45 ` Linus Torvalds
2004-10-10 19:04   ` Maciej W. Rozycki
2004-10-10 21:19     ` [ACPI] " Sérgio Monteiro Basto
2004-10-11  1:44       ` Maciej W. Rozycki
2004-10-11  2:44         ` Linus Torvalds
2004-10-11  0:47     ` Linus Torvalds
2004-10-11 11:42       ` Andi Kleen [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=20041011114211.GF14615@wotan.suse.de \
    --to=ak@suse.de \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=torvalds@osdl.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