public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Leo L. Schwab" <ewhac@best.com>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: acpi_video_flags Reset on Resume-From-RAM
Date: Sun, 4 Nov 2007 12:41:50 +0000	[thread overview]
Message-ID: <20071104124149.GD3921@ucw.cz> (raw)
In-Reply-To: <20071009000038.GA23726@best.com>

On Mon 2007-10-08 17:00:38, Leo L. Schwab wrote:
> 	Suspend-to-RAM used to (mostly) work on this machine, but there
> seems to have been a regression between 2.6.22.1 and 2.6.22.5.
> 
> 	I have a ThinkPad Z61t, with an Intel Core 2 Duo and Intel 945GM
> graphics.  My kernel command line contains the argument,
> "acpi_sleep=s3_bios,s3_mode", which is the same as setting
> /proc/sys/kernel/acpi_video_flags to 3.  This setting is suggested by
> ThinkWiki.org for getting the Intel graphics to recover properly after
> suspend-to-RAM.
> 
> 	Under 2.6.22.1, this arrangement worked fine.  However, since I
> upgraded the kernel to 2.6.22.5, the text console refuses to come back.
> When I inspect acpi_video_flags, the value has been reset to zero.
> 
> 	Sequence:
> 	- Boot system.
> 	- Inspect /proc/sys/kernel/acpi_video_flags -- it contains 3.
> 	- Trigger suspend-to-RAM (done via 'hibernate-ram').  I have
> 	  configured 'hibernate' to leave acpi_video_flags alone.
> 	- Resume system.  Text console does not come back.  I can force X to
> 	  recover the display by pressing CTRL-ALT-F1 (switch to console)
> 	  followed by ALT-F7 (switch to X).
> 	- Inspect /proc/sys/kernel/acpi_video_flags -- it contains 0.
> 	- Force acpi_video_flags back to 3:
> 	  echo 3 > /proc/sys/kernel/acpi_video_flags
> 	- Inspect /proc/sys/kernel/acpi_video_flags -- it contains 3.
> 	- Trigger suspend-to-RAM.
> 	- Resume system.  Text console does not come back.  acpi_video_flags
> 	  contains zero again.
> 
> 	I'm running a custom-compiled kernel (config available upon
> request).  The highlights are SMP, PREEMPT, and NOHZ.
> 
> 	Note that nothing short of a full reboot will restore the console.
> Switching to a virtual console results in a blank screen.  Switching back to
> X so far always works.  Since the console's busted, it's not immediately
> clear how I might diagnose this further.  Suggestions?

Try updating to 2.6.24-rc.... Or find out which patch causes the
regression, and talk to its author.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2007-11-04 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09  0:00 acpi_video_flags Reset on Resume-From-RAM Leo L. Schwab
2007-11-04 12:41 ` Pavel Machek [this message]

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=20071104124149.GD3921@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ewhac@best.com \
    --cc=linux-pm@lists.linux-foundation.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