From: Sebastian Kloska <kloska@scienion.de>
To: linux-kernel@vger.kernel.org
Subject: Re: APM realy sucks on 2.6.x
Date: Mon, 07 Jun 2004 10:11:48 +0200 [thread overview]
Message-ID: <40C42344.30908@scienion.de> (raw)
Denis Vlasenko wrote:
>On Saturday 05 June 2004 20:18, Sebastian Kloska wrote:
>
>
>> Thanks for the patch
>>
>> Unfortunately that didn't do the trick. It does not even suspend
>> sometimes when hitting the suspend button. This is very strange.
>> It reproducible does not resume the second time. Seems like
>> the system has been left in an unstable state after the first
>> suspend/resume cycle. I'm definitely not the born hardware/BIOS
>> programmer although I have been involved in graphic device
>> programming (a pain) but in this this case which is a real pain I
>> would be willing to at least help by further debugging the issue.
>> Kernel 2.4.x proved that the BIOS can be talked into properly
>> interacting with linux. So it's at least not totally brain dead.
>>
>> One might argue that the hardware is already a little bit out dated
>> but I really do not have the resources to buy a new
>> laptop every year and it also represents some kind of masochistic
>> challenge to get this thing going. But I really do not know how
>> to debug the stuff or where to look.
>>
>> Any hints how to proceed would be highly appreciated
>>
>>
>
>
>
>Well, typically I pepper source with printks, rebuild kernel,
>reboot, set loglevel to max, watch the log, crash, repeat.
>
>
Realy was afraid you say something like this. Now I'll follow
Michael Clarks recommentation of ripping down the kernel
to minimal functionality and add drivers/moduls until I hit
the 'bad' one. ... keep you informed
>--
>vda
>
>
>
--
**********************************
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 reply other threads:[~2004-06-07 8:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 8:11 Sebastian Kloska [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-08 9:49 APM realy sucks on 2.6.x Sau Dan Lee
2004-06-04 21:26 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
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
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=40C42344.30908@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