From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Marcus Better <marcus@better.se>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
pavel@suse.cz, linux-pm@lists.osdl.org,
Adrian Bunk <bunk@stusta.de>
Subject: Re: [3/3] 2.6.21-rc6: known regressions
Date: Tue, 17 Apr 2007 17:27:56 +0800 [thread overview]
Message-ID: <1176802076.6227.2.camel@daplas> (raw)
In-Reply-To: <200704171017.07012.marcus@better.se>
On Tue, 2007-04-17 at 10:17 +0200, Marcus Better wrote:
> > Have you tried other combinations?
> >
> > s2ram -m -p -f
> > s2ram -s -p -f
>
> Yes, I tried these slightly different combinations:
>
> s2ram -f -a3 -s: Works! The screen becomes green but is restored quickly. It
> prints the following messages:
> Allocated buffer at 0x11000 (base is 0x0)
> ES: 0x1100 EBX: 0x0000
> Save video state failed
> Calling restore_state_from
> Function not supported?
> Restore video state failed
> Switching back to vt1
>
> s2ram -f -a3 -p: Screen goes green and then blank. Everything hangs, doesn't
> react to keyboard input.
>
> s2ram -f -a3 -m: Works!
>
Thanks. Should we consider this regression resolved? There is really
nothing much vesafb can do to restore its previous state, except through
the use of userland tools.
Tony
next prev parent reply other threads:[~2007-04-17 9:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0704051944230.6730@woody.linux-foundation.org>
[not found] ` <20070413212954.GA2545@melchior.yamamaya.is-a-geek.org>
2007-04-13 23:50 ` Linux 2.6.21-rc6 Adrian Bunk
2007-04-14 6:50 ` Tobias Diedrich
2007-04-14 8:16 ` Tobias Diedrich
2007-04-14 9:05 ` Rafael J. Wysocki
2007-04-14 10:32 ` Tobias Diedrich
2007-04-14 12:26 ` Adrian Bunk
2007-04-14 12:09 ` Tobias Diedrich
2007-04-14 12:24 ` Tobias Diedrich
2007-04-14 12:31 ` Tobias Diedrich
2007-04-14 13:00 ` Adrian Bunk
2007-04-14 18:28 ` Rafael J. Wysocki
2007-04-14 19:56 ` Tobias Diedrich
2007-04-14 20:23 ` Rafael J. Wysocki
2007-04-14 20:25 ` Adrian Bunk
2007-04-14 20:38 ` Rafael J. Wysocki
2007-04-14 21:35 ` Tobias Diedrich
2007-04-14 21:58 ` Rafael J. Wysocki
2007-04-15 7:38 ` Tobias Diedrich
2007-04-15 8:02 ` Tobias Diedrich
2007-04-15 11:16 ` Rafael J. Wysocki
2007-04-15 14:19 ` Dmitry Torokhov
2007-04-15 15:52 ` Rafael J. Wysocki
2007-04-15 18:50 ` Tobias Diedrich
2007-04-15 19:37 ` Rafael J. Wysocki
2007-04-15 15:14 ` David Brownell
2007-04-15 16:37 ` Rafael J. Wysocki
2007-04-15 17:53 ` David Brownell
2007-04-15 19:40 ` [linux-pm] " Tobias Diedrich
2007-04-15 19:54 ` Rafael J. Wysocki
2007-04-25 17:14 ` [linux-pm] " Tobias Diedrich
2007-04-25 19:36 ` Rafael J. Wysocki
2007-04-25 20:09 ` [linux-pm] " Tobias Diedrich
2007-04-14 0:38 ` [3/3] 2.6.21-rc6: known regressions Adrian Bunk
2007-04-14 1:57 ` Antonino A. Daplas
2007-04-15 16:26 ` Marcus Better
2007-04-15 23:08 ` Antonino A. Daplas
2007-04-16 6:23 ` Marcus Better
2007-04-16 6:45 ` Antonino A. Daplas
2007-04-17 8:17 ` Marcus Better
2007-04-17 9:27 ` Antonino A. Daplas [this message]
2007-04-17 11:54 ` Marcus Better
2007-04-24 15:33 ` Pavel Machek
2007-04-14 7:40 ` Dave Jones
2007-04-15 17:15 ` Jeff Chua
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=1176802076.6227.2.camel@daplas \
--to=adaplas@gmail.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=marcus@better.se \
--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