public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Kloska <kloska@scienion.de>
To: linux-kernel@vger.kernel.org
Subject: APM realy sucks on 2.6.x
Date: Fri, 04 Jun 2004 23:26:53 +0200	[thread overview]
Message-ID: <40C0E91D.9070900@scienion.de> (raw)

Hi

I'm really having a hard time with APM on 2.6.x. I have a DELL Latitude
L400 with the newest BIOS release. The most important functionality
of  APM  for  me  is  the  'suspend to RAM' function which worked like
it should on all 2.4.x kernels I've tested. Under 2.6.x it simply does 
not resume the second
time. Meaning it suspends and resumes once but when suspending the second
time the machine only brings up the LEDs and FAN and is stucked. I've
modified the kernel option for APM but that did not help at all.

I've already stated that question here and googled my fingers down to the
bones. The discussion always goes in these directions:

(1) Wait until ACPI is fully functional. Although a lot of people claim that
there are a lot of BIOses around that do not implement it properly and that
even MS-evel Windows has its problems with it.

(2) Exchange the motherboard.

(3) Buy a decent computer.

(4) Stick with 2.4.x

(5) And so on and so forth

All of this is not very constructive.

My impression is that APM is slowly degenerating while ACPI is not
(yet ?) able to fill the gap. The suspend feature of ACPI is stated to
be dangerous and experimental and does not work for me at all.

After all this bashing...

Is there anyone out there who has the same experiences ?

Is there a workaround ?

Is it possible to somehow downgrade APM in the 2.6 kernel
to the 2.4.x state ?

How could one debug this kind of missbehaviour ? Where do
I have to look for potential miss configurations of the system ?

I'm really willing  to help the APM developers to track down this bug
but don't have a clue how to debug this kind stuff.

Thanks for your attention

Sebastian





             reply	other threads:[~2004-06-04 21:18 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 21:26 Sebastian Kloska [this message]
2004-06-04 23:14 ` APM realy sucks on 2.6.x Keith Duthie
2004-06-05  8:03   ` Sebastian Kloska
2004-06-04 23:54 ` Hugh Dickins
2004-06-05 17:18   ` Sebastian Kloska
2004-06-06  3:29     ` Michael Clark
2004-06-06  4:25       ` Andrew Morton
2004-06-06 13:56         ` Sebastian Kloska
2004-06-07 12:38 ` Pavel Machek
2004-06-07 13:37   ` Sebastian Kloska
2004-06-07 14:05     ` Pavel Machek
2004-06-07 14:28       ` Sebastian Kloska
2004-06-07 14:48         ` Pavel Machek
2004-06-07 19:53           ` Felipe Alfaro Solana
2004-06-07 21:13             ` Sebastian Kloska
2004-06-08  4:16           ` Clemens Schwaighofer
2004-06-08  7:12             ` Sebastian Kloska
2004-06-08  8:58             ` Pavel Machek
2004-06-08  9:02               ` Clemens Schwaighofer
2004-06-08  9:17                 ` Pavel Machek
2004-06-08  9:50                   ` Clemens Schwaighofer
2004-06-08  9:55                     ` Pavel Machek
2004-06-08 23:59                       ` Clemens Schwaighofer
2004-06-08 17:48               ` Bill Davidsen
2004-06-08 18:59                 ` Daniel Gryniewicz
2004-06-08 20:18                 ` Ian Stirling
2004-06-07 14:42     ` Keith Duthie
2004-06-07 14:44       ` Pavel Machek
2004-06-07 14:47       ` Sebastian Kloska
2004-06-07 14:51         ` Pavel Machek
2004-06-07 15:09           ` Sebastian Kloska
2004-06-07 16:26             ` Pavel Machek
2004-06-07 15:19         ` Keith Duthie
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07  8:11 Sebastian Kloska
2004-06-08  9:49 Sau Dan Lee

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=40C0E91D.9070900@scienion.de \
    --to=kloska@scienion.de \
    --cc=linux-kernel@vger.kernel.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