From: Johan Vromans <jvromans@squirrel.nl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: swsusp problems with 2.6.17-1.2139_FC5
Date: Thu, 29 Jun 2006 19:15:40 +0200 [thread overview]
Message-ID: <m2irmj9937.fsf@phoenix.squirrel.nl> (raw)
swsusp has problems resumeing after upgrading my Acer Travelmate
4001WLMi from 2.6.16 to 2.6.17. Note that I'm running a Fedora 5
kernel, with the ATI proprietary video driver.
On this 512Mb system, I have typically 60% of memory in use when I go
into hibernate. This is with X, wm, Emacs, some xterms, wireless.
With 2.6.16, when I initiate a hibernate with
echo shutdown > /sys/power/disk; echo disk > /sys/power/state
I get switched back to vt1(?), the "stopping tasks" messages, and so
on, until the system shuts down in ordinary fashion.
With 2.6.17, when I initiate the hibernate, I get no apparent reaction
(although the flashing disk led reveals what's going on) and the
system shuts down.
Upon reboot, I get
Trying to resume from /dev/hda4
Resuming from /dev/hda4.
Attempting manual resume
and then the console does a half-hearted attemtp to restore X and
freezes. The system is alive, I can login via the network. Restarting
the X server (from another tty, the console remains stuck) seems to
'cure' the problem. However, when exiting X the console stays
connected to vt7 and needs to be put back to vt1 manually.
It seems to be a problem with the video switching out/in X.
When I change to a vt out of X, then suspend/resume seems to give no
problem and after resume I can switch back to vt7 into X.
Any suggestions to cure this problem? Is it a know regression?
Thanks,
Johan
next reply other threads:[~2006-06-29 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 17:15 Johan Vromans [this message]
2006-06-29 19:25 ` swsusp problems with 2.6.17-1.2139_FC5 Rafael J. Wysocki
2006-06-30 18:01 ` Pavel Machek
2006-06-30 20:22 ` Johan Vromans
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=m2irmj9937.fsf@phoenix.squirrel.nl \
--to=jvromans@squirrel.nl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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