All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Kloska <kloska@scienion.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM realy sucks on 2.6.x
Date: Mon, 07 Jun 2004 15:37:03 +0200	[thread overview]
Message-ID: <40C46F7F.7060703@scienion.de> (raw)
In-Reply-To: <20040607123839.GC11860@elf.ucw.cz>

Pavel Machek wrote:
> Hi!
> 
> 
>>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.
> 
> 
> That sounds about right.
> 
> 
>>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.
> 
> 
> What APM developers? There are none as far as I know.


   Hmmm ... So once again the Tooth Fairy and Santa Claus :-) ?

   At least a

   grep '<.*@' /usr/src/linux-2.6.6/arch/i386/kernel/apm.c | sed 's/.*<//' | sed 's/>.*//'

   gives me:

<snip>
Ulrich.Windl@rz.uni-regensburg.de
jtoth@princeton.edu
gaudet@arctic.org
cananian@alumni.princeton.edu
echter@informatik.uni-rostock.de
rankinc@bellsouth.net
cmiller@surfsouth.com
rgooch@atnf.csiro.au
rgooch@atnf.csiro.au
laslo@wodip.opole.pl
ross@soi.city.ac.uk
borislav@lix.polytechnique.fr
sitta@al.unipmn.it
teras@writeme.com
Walter.Hofmann@physik.stud.uni-erlangen.de
skawina@geocities.com
rusty@rustcorp.com.au
gis88564@cis.nctu.edu.tw
jima@hal.com
alan@lxorguk.ukuu.org.uk
jima@hal.com
andy_henroid@yahoo.com
pavel@suse.cz
andy_henroid@yahoo.com
zlatko@iskon.hr
crutcher+kernel@datastacks.com
arjanv@redhat.com
marc@mbsi.ca
alan@redhat.com
alan@redhat.com
jdthood@mail.com
chief@bandits.org
ast@domdv.de
rmk@arm.linux.org.uk
jdthood@mail.com
reese@isn.net
neale@lowendale.com.au
cmiller@surfsouth.com
chen@ctpa04.mit.edu
</snip>

This is pretty much for no one. And I guess you knew since you're on
the list yourself. But I think you're right when meaning
that there is not much of active maintenance anymore. Which at
least I find a little bit discouraging when looking of the state
of the ACPI support.


> 
> Try removing calls to device_* in apm.c. Better yet become APM
> developer.

   It seems like I'm on my way to do so (still reluctantly). As I stated
  in my previous mails I'm not born as a hardware/BIOS hacker (more the
  application C++/Java stuff) but I'm willing to learn. When I'm
  grown up I definitely want to be linux kernel hacker :-) ...

   Currently I ripped down the 2.6.6 kernel to almost nothing
  and add one module after the other checking for proper
  suspend/resume behavior....

   The most suspicious candidates on my list are currently  the
  USB-UHCI driver and the ALSA sound system, which is my #1 candidate
  since it has not been an integral part of the 2.4.x (x<=20) kernels.


  So if anybody out there could give me guidance on how the apm code
  might interact with the ALSA sound system it would be highly
  appreciated....

  Thanks

  Sebastian



> 							Pavel

  reply	other threads:[~2004-06-07 13:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 21:26 APM realy sucks on 2.6.x Sebastian Kloska
2004-06-04 23:14 ` 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 [this message]
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=40C46F7F.7060703@scienion.de \
    --to=kloska@scienion.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.