From: Malte Doersam <malte.d-hi6Y0CQ0nG0@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: How to debug not working S3?
Date: Fri, 18 Jul 2003 00:42:34 +0200 [thread overview]
Message-ID: <200307180042.35263.malte.d@gmx.net> (raw)
Hi everybody,
I'm curious how you get some usefull information on which point the resume
might fail. I'm just trying 2.6-test0 with ACPI revision 20030714 and S1
works quite fine, but S3 is nasty.
Computer: Thinkpad R31 i810 laptop
if I echo 3 to /proc/acpi/sleep all the processes are moved to the
refrigerator and the laptop turns itself off. Invoking any acpi-event makes
the Thinkpad waking up, I hear the harddrive spinning up for like a second
and then turning off again. After this, the system is kinda dead and must be
turned off the hard way. (pressing the power button for 4 seconds).
I'd like to gather some information on the problem, which prevents resuming.
Any hint/note on how to do this?
cheers Malte
P.S. there is a bug on bugzilla filed in the category 'input devices' but is
probably acpi related: http://bugzilla.kernel.org/show_bug.cgi?id=804
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
next reply other threads:[~2003-07-17 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 22:42 Malte Doersam [this message]
[not found] ` <200307180042.35263.malte.d-hi6Y0CQ0nG0@public.gmane.org>
2003-07-18 8:41 ` How to debug not working S3? Ole Myren Rohne
-- strict thread matches above, loose matches on Subject: below --
2004-08-08 15:19 How to debug (not working)S3? Gruetzner-Mmb7MZpHnFY
2004-08-08 16:01 Stefan Schweizer
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=200307180042.35263.malte.d@gmx.net \
--to=malte.d-hi6y0cq0ng0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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