mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Ruben Puettmann <ruben@puettmann.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22 APM problems with IBM Thinkpad's
Date: Wed, 13 Aug 2003 16:24:40 +0200	[thread overview]
Message-ID: <16186.18984.335521.224346@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030813133126.GA26337@puettmann.net>

Ruben Puettmann writes:
 > 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.

Several reasons:
- The interaction wasn't understood initially, and some problems
  didn't start appearing until late last year. The problems are
  also system & configuration dependent.
  Case in point #1: my P3B-F and P4T-E ASUS mainboards never had
  problems until they started running 2.5 kernels, where HZ==1000
  greatly increased the likelihood of a local APIC timer interrupt
  while in BIOS screen blanking code.
  Case in point #2: my TUSL2-C ASUS mobo (RIP) worked great until
  I switched from a Millenium to a Radeon 8500, and found that it
  hung because of local APIC timer interrupts while in BIOS screen
  blanking code, even in 2.4 kernels.
- Fixing the APM driver would require that someone who understands
  it modifies it to avoid BIOS calls (other than suspend/resume) when
  UP_APIC is active. I'm not that person.
- The problems can be worked around by avoiding misconfigurations.

  reply	other threads:[~2003-08-13 14:24 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 [this message]
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=16186.18984.335521.224346@gargle.gargle.HOWL \
    --to=mikpe@csd.uu.se \
    --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®