From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: suspend/resume fails on second attempt in LNXVIDEO:00
Date: Thu, 18 Dec 2008 04:24:44 +0000 (UTC) [thread overview]
Message-ID: <gicjac$m5f$11@ger.gmane.org> (raw)
In-Reply-To: 200812160002.43427.rjw@sisk.pl
On Tue, 16 Dec 2008 00:02:43 +0100, Rafael J. Wysocki wrote:
>
> You can try to use the s2ram binary (http://en.opensuse.org/s2ram) to
> work around this issue.
OK. I've done my s2ram experiments and go no better than with pm-utils/
kernel mode suspend (where first suspend/resume works, second suspend
works, but second resume hangs the machine). Here's the full array of
suggestions on http://en.opensuse.org/S2ram and their results:
s2ram -f -a 3
- hung on first resume
s2ram -f -a 2
- restored first resume but no backlight
s2ram -f -a 1
- hung on first resume
s2ram -f -p -m
- resumed first time but console font changed
- hung on second resume
s2ram -f -p -s
- resumed first time but console font changed
- hung on second resume
s2ram -f -m
- restored first resume but no backlight
s2ram -f -s
- resumed first time but console font changed
- message "Function not supported?\nSwitching back to vt1"
- hung on second resume
s2ram -f -p
- resumed first time but console font changed
- hung on second resume
s2ram -f -a 2 -m
- restored first resume but no backlight
s2ram -f -a 2 -s
- resumed first time but console font changed
- message "Function not supported?\nSwitching back to vt1"
These were always booting with init=/bin/bash and removing all removable
(i.e. unreferenced) modules.
Where I mention "console font changed" that means it reverted back to the
font that it was in when it was booting the kernel. You see, Ubuntu, at
some point through boot actually change the font to be a "leaner" (i.e.
not so "fat") font. This is not to say that I am running on the console
in a framebuffer (to the best of my knowledge). I believe this font
setting is being done with a "/usr/bin/consolechars" tool.
Anyway, thanx much for continuing to look into this.
Cheers,
b.
next prev parent reply other threads:[~2008-12-18 4:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 5:06 suspend/resume fails on second attempt in LNXVIDEO:00 Brian J. Murrell
2008-12-14 6:43 ` Justin P. Mattock
2008-12-14 20:55 ` Brian J. Murrell
2008-12-14 22:29 ` Justin P. Mattock
2008-12-15 15:56 ` Pavel Machek
2008-12-15 17:00 ` Brian J. Murrell
2008-12-15 17:33 ` Alexey Starikovskiy
2008-12-15 17:56 ` Brian J. Murrell
2008-12-15 20:19 ` Rafael J. Wysocki
2008-12-15 20:52 ` Brian J. Murrell
2008-12-15 23:02 ` Rafael J. Wysocki
2008-12-16 2:34 ` Brian J. Murrell
2008-12-16 15:25 ` Rafael J. Wysocki
2008-12-16 16:02 ` Brian J. Murrell
2008-12-16 16:13 ` Rafael J. Wysocki
2008-12-16 16:18 ` Brian J. Murrell
2008-12-16 16:22 ` Rafael J. Wysocki
2008-12-16 23:54 ` Brian J. Murrell
2008-12-16 16:37 ` Matthew Garrett
2008-12-16 18:07 ` Brian J. Murrell
2008-12-16 20:53 ` Matthew Garrett
2008-12-18 7:52 ` Pavel Machek
2008-12-18 8:11 ` Justin P. Mattock
2008-12-18 4:24 ` Brian J. Murrell [this message]
2008-12-18 23:57 ` Brian J. Murrell
2008-12-19 17:33 ` Rafael J. Wysocki
2008-12-19 21:10 ` Brian J. Murrell
2008-12-20 17:43 ` Sergio Monteiro Basto
2008-12-20 21:08 ` Brian J. Murrell
2008-12-14 9:16 Robby Workman
2008-12-14 14:08 ` Brian J. Murrell
2008-12-14 15:35 ` Justin P. Mattock
2008-12-14 17:06 ` Brian J. Murrell
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='gicjac$m5f$11@ger.gmane.org' \
--to=brian@interlinx.bc.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.