From: Peter Meier <crazy-b-Mmb7MZpHnFY@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Suspend to ram broken for me with 2.6.5-mm3 (2.6.4 worked)
Date: Sat, 10 Apr 2004 17:21:49 +0200 [thread overview]
Message-ID: <1081610508.10947.140.camel@homer> (raw)
Hi,
actually, I'm not abled to wake up from suspend to ram with 2.6.5-mm3.
Monitor stays black, fans are making noise forever, but nothing. Network
is dead, too.
I had no problems with suspend to ram untill 2.6.4 (X with in10, unload usb and sound before sleep, use the fixpci script of Stefan Dösinger to get sound working after a wake up). I did not change any kernel configuration options or anything else. 2.6.5-rc2-mm5, 2.6.5-rc3-mm4 have the same problems, as 2.6.5-rc3-mm1, as all 2.6.5-mm*. So somewhere between 2.6.4 and 2.6.5-rc2 something changed which broke it for me.
The only difference I noticed so far is, with the 'broken' kernels, I
see "PM Entering state" as last thing before the system goes to sleep.
With the working kernels, I see more lines before the "PM Entering
state" and system goes to sleep (something with hda, acpi, etc., several
lines)
Notebook is an Acer Travelmate 803 (Radeon Mobility 9000, Centrino).
I'll provide further details on request.
With best regards,
Peter
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-04-10 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 15:21 Peter Meier [this message]
[not found] ` <1081610508.10947.140.camel-0dCjsm2Eg2I@public.gmane.org>
2004-04-14 16:42 ` Suspend to ram broken for me with 2.6.5-mm3 (2.6.4 worked) Stefan Dösinger
-- strict thread matches above, loose matches on Subject: below --
2004-04-12 1:36 Ow Mun Heng
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=1081610508.10947.140.camel@homer \
--to=crazy-b-mmb7mzphnfy@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