From: Mikael Pettersson <mikpe@csd.uu.se>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ruben Puettmann <ruben@puettmann.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.22 APM problems with IBM Thinkpad's
Date: Wed, 13 Aug 2003 16:32:39 +0200 [thread overview]
Message-ID: <16186.19463.54075.109122@gargle.gargle.HOWL> (raw)
In-Reply-To: <1060783884.8008.64.camel@dhcp23.swansea.linux.org.uk>
Alan Cox writes:
> On Mer, 2003-08-13 at 14:13, Mikael Pettersson wrote:
> > With APIC support enabled (SMP or UP_APIC), APM must be constrained:
> > DISPLAY_BLANK off
> > CPU_IDLE off
> > built-in driver, not module
>
> This isnt sufficient because some of the SMM traps off the FN-key
> sequences also crash thinkpads if APIC is enabled. Basically *dont use
> local apic* except on SMP.
For those Thinkpads a DMI blacklist entry should suffice.
(Just like it solved the Inspiron problems.)
2.6-mm has the "lapic" and "nolapic" options I added so that
P4s no longer are autoenabled, needed for broken ACPI BIOSen.
Perhaps we should require the "lapic" option also for all P6s?
(Strangely, K7 machines seem to have fewer local APIC BIOS issues
than either P6 or P4 machines.)
next prev parent reply other threads:[~2003-08-13 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 12:31 Ruben Puettmann
2003-08-13 13:13 ` Mikael Pettersson
2003-08-13 13:31 ` Ruben Puettmann
2003-08-13 14:24 ` Mikael Pettersson
2003-08-13 14:11 ` Alan Cox
2003-08-13 14:32 ` Mikael Pettersson [this message]
2003-08-14 12:28 ` Ruben Puettmann
2003-08-14 13:21 ` Mikael Pettersson
2003-08-14 13:47 ` Alan Cox
2003-08-14 17:33 ` Jamie Lokier
2003-08-14 20:03 ` Mikael Pettersson
2003-08-14 21:40 ` Jamie Lokier
[not found] ` <20030813131043.GA1112@deimos.one.pl>
2003-08-13 13:35 ` Ruben Puettmann
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=16186.19463.54075.109122@gargle.gargle.HOWL \
--to=mikpe@csd.uu.se \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ruben@puettmann.net \
/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®