From: Johan Vromans <jvromans@squirrel.nl>
To: Pavel Machek <pavel@suse.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: swsusp problems with 2.6.17-1.2139_FC5
Date: Fri, 30 Jun 2006 22:22:04 +0200 [thread overview]
Message-ID: <m2y7vetmvn.fsf@phoenix.squirrel.nl> (raw)
In-Reply-To: <20060630180141.GC9225@elf.ucw.cz> (Pavel Machek's message of "Fri, 30 Jun 2006 20:01:41 +0200")
Pavel Machek <pavel@suse.cz> writes:
> Stop right here. Can you reproduce the problem without ATI driver?
> Reproducing it on vanilla kernel (not -FC5) would be nice, too.
A lot of suspend/reboot/resumes later...
The problem does not seem to be related to the ATI driver, but whether
or not the pm-suspend program is used. With the Xorg driver I get the
same problem when I suspend with
echo shutdown > /sys/power/disk; echo disk > /sys/power/state
When I use pm-hibernate suspend/resume seems works okay (with Xorg and
ATI driver).
With 2.6.16, I did not have the need to use pm-hibernate. So something
changed here.
As mentioned in my OP using pm-hibernate does not give any feedback
what is going on (except for the disk led). I find this annoying.
Another annoyance is that pm-hibernate locks this kernel for the next
reboot, so it is not possible to boot something else and resume
later.
Apart from that, suspend/resume is a life saver!
(Now it would be nice to get suspend to memory working. It seems to
suspend okay, but I haven't found out how to resume...)
-- Johan
next prev parent reply other threads:[~2006-06-30 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 17:15 swsusp problems with 2.6.17-1.2139_FC5 Johan Vromans
2006-06-29 19:25 ` Rafael J. Wysocki
2006-06-30 18:01 ` Pavel Machek
2006-06-30 20:22 ` Johan Vromans [this message]
2006-06-30 21:16 ` Pavel Machek
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=m2y7vetmvn.fsf@phoenix.squirrel.nl \
--to=jvromans@squirrel.nl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.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