From: Ruben Puettmann <ruben@puettmann.net>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22 APM problems with IBM Thinkpad's
Date: Wed, 13 Aug 2003 15:31:26 +0200 [thread overview]
Message-ID: <20030813133126.GA26337@puettmann.net> (raw)
In-Reply-To: <16186.14686.455795.927909@gargle.gargle.HOWL>
On Wed, Aug 13, 2003 at 03:13:02PM +0200, Mikael Pettersson wrote:
>
> This sounds like a well-known APM/local-APIC clash.
nice to know ...
>
> Never ever use DISPLAY_BLANK if you also have SMP or UP_APIC.
not nice so ;-( how is it with acpi? Same problem?
> With APIC support enabled (SMP or UP_APIC), APM must be constrained:
> DISPLAY_BLANK off
> CPU_IDLE off
> built-in driver, not module
Why will this not be disabled in make *config so that nobody will run in
this problem?
> This is because the apm driver does BIOS calls, and many BIOSen
> (including the code in graphics cards, e.g. all Radeons it seems)
> like to hang if a local APIC timer interrupt arrives.
Yes radeonfb don't like apm -s on this thinkpad. apm -s works but on
resume it freezed some on
modprobe radeonfb;
sleep 10;
rmmod radeonfb;
sleep 10;
modprobe radeonfb;
and thinkpad freezed .
Ruben
--
Ruben Puettmann
ruben@puettmann.net
http://www.puettmann.net
next prev parent reply other threads:[~2003-08-13 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 12:31 2.4.22 APM problems with IBM Thinkpad's Ruben Puettmann
2003-08-13 13:13 ` Mikael Pettersson
2003-08-13 13:31 ` Ruben Puettmann [this message]
2003-08-13 14:24 ` Mikael Pettersson
2003-08-13 14:11 ` Alan Cox
2003-08-13 14:32 ` Mikael Pettersson
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=20030813133126.GA26337@puettmann.net \
--to=ruben@puettmann.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.