From: Avuton Olrich <avuton-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Asus A7N8X not resuming with 2.6.13-rc6-mm1, worked with 2.6.13-rc5-mm1
Date: Fri, 19 Aug 2005 11:37:41 -0700 [thread overview]
Message-ID: <3aa654a4050819113778c4d4b0@mail.gmail.com> (raw)
Hello,
My Asus A7N8X worked previously with the 2.6.13-rc5-mm1, as was the
subject of the thread:
http://marc.theaimsgroup.com/?t=112339603900001&r=1&w=2
and the bugzilla bug:
http://bugzilla.kernel.org/show_bug.cgi?id=4723
With linux-2.6.13-rc6-mm1 resume has stopped working again. For any
information you need to know about the system, I put very verbose logs
at the bugzilla link and they are all still valid.
What happens is:
Here's my script to sucessfully shutdown and resume in 2.6.13-rc5-mm1,
all of the following must be done with X stopped and the nvidia module
unloaded.
# sync
# echo "mem" > /sys/power/state
# vbetool post
And like magic it just works.
What happens with 2.6.13-rc6-mm1:
(the 3 lines from before), I can ping the machine for 8 seconds, (I
could probably ssh into it if I were quick) then I can hear the
harddrives stop and the computer and power supply continue to run as
if it went into standby (echo standby > /sys/power/state). I see no
messages in the syslog.
How can I help?
thanks,
avuton
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
reply other threads:[~2005-08-19 18:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3aa654a4050819113778c4d4b0@mail.gmail.com \
--to=avuton-re5jqeeqqe8avxtiumwx3w@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