From: Christian Leber <christian@leber.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: beeping patch for debugging acpi sleep
Date: Sat, 16 Jun 2007 21:46:34 +0200 [thread overview]
Message-ID: <20070616194634.GA15953@core> (raw)
In-Reply-To: <20070609130817.GI27793@elf.ucw.cz>
On Sat, Jun 09, 2007 at 03:08:17PM +0200, Pavel Machek wrote:
> Starting beeper as soon as ACPI sleep returns is very useful in
> debugging "apparently dead" machines. If it beeps at all, it makes
> sense to start playing with CMOS tracer.
thank you very much Pavel
The results are a bit unclear, I took a 2.6.22-rc4 with beep.
Logged into KDE.
(hardware: Dell Latitude D810)
S = successfull resume
D = had to resume 2 times, that means when pressing the power button the
LED goes from blinking to on and after a few seconds it goes back to
blinking, but without a beep in between; after pressing the power button
a second time resume is successfull
F = resume failes, NO beep
-run 1: D D F
-run 2: D D D(some X garbadge) F
-run 3: S S S S S S F
-run 4: S S F
-run 5: D F
Very odd, nothing was changed in between and after each F i switched it
off... because it was dead.
With 2.6.19.7 i have never seen it fail.
Christian Leber
--
http://rettetdieti.vde-uni-mannheim.de/
next prev parent reply other threads:[~2007-06-16 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070518213701.GA810@core>
2007-05-18 22:45 ` [BUG] acpi double resume and fail Andrew Morton
2007-05-19 19:42 ` Christian Leber
[not found] ` <20070520200142.GB5235@ucw.cz>
[not found] ` <20070602182014.GB29546@core>
[not found] ` <20070609130817.GI27793@elf.ucw.cz>
2007-06-16 19:46 ` Christian Leber [this message]
2007-06-24 20:46 ` beeping patch for debugging acpi sleep Christian Leber
2007-06-28 14:08 ` Pavel Machek
2007-08-12 21:37 ` Christian Leber
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=20070616194634.GA15953@core \
--to=christian@leber.de \
--cc=akpm@osdl.org \
--cc=linux-acpi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).