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 16:28:36 +0200 [thread overview]
Message-ID: <40C47B94.6040408@scienion.de> (raw)
In-Reply-To: <20040607140511.GA1467@elf.ucw.cz>
Hi again
Thanks for the hint on device_suspend (realy !! gives me a starting point
for debugging.
Pavel Machek wrote:
> Hi!
>
>
>>>>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
>
> ...
>
>>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.
>
>
> Yes, that's pretty much what I meant. ACPI has ~5 people actively
> working on it, some of them probably full-time. That's a lot of
> manpower, compared to APM.
This becomes a little bit scary. Someone else on this list already
mentioned that there is a strong movement towards everything which
is at least a desktop/server machine. And on the other hand there are
these embedded systems which seem to be attractive for linux to.
ACPI seems to be nifty for such things like hardware monitoring and
stuff. That makes it interesting for servers etc...
Everything in the middle (aka laptops) seems to slowly drop out of the
loop. PCMCIA seems to be another ugly example. Anyway ... I'm not frightened
by this manpower. Just want to have my laptop running 2.6.x and suspending
to RAM. I'll do my very best and report back if there are any significant
findings.....
>
> And ACPI is in pretty good state, btw, unless you want
> suspend-to-RAM. Unfortunately you want suspend-to-RAM.
>
>
>>>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....
>
>
> device_suspend() will propagate all the way to alsa.
> Pavel
--
**********************************
Dr. Sebastian Kloska
Head of Bioinformatics
Scienion AG
Volmerstr. 7a
12489 Berlin
phone: +49-(30)-6392-1708
fax: +49-(30)-6392-1701
http://www.scienion.de
**********************************
next prev parent reply other threads:[~2004-06-07 14:28 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
2004-06-07 14:05 ` Pavel Machek
2004-06-07 14:28 ` Sebastian Kloska [this message]
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=40C47B94.6040408@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox