From: Thomas Gleixner <tglx@linutronix.de>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>,
pavel@suse.cz, linux-pm@osdl.org, linux-acpi@vger.kernel.org,
len.brown@intel.com, mingo@redhat.com
Subject: Re: 2.6.21-rc1: T60 resume from suspend to RAM issues
Date: Sun, 25 Feb 2007 10:03:41 +0100 [thread overview]
Message-ID: <1172394221.25076.359.camel@localhost.localdomain> (raw)
In-Reply-To: <20070222233803.GA4447@mellanox.co.il>
On Fri, 2007-02-23 at 01:38 +0200, Michael S. Tsirkin wrote:
> 1. After suspend to RAM, system wakes up but no screen.
> I can log in through ssh though.
> dmesg output at this point below.
> Works fine on 2.6.20 and below, with same .config
> .config and log file for this issue attached.
>
> 2. As a separate test, I enabled DynTicks in .config.
> Seems to work fine but won't come out of suspend to memory at all:
> pressing Fn/F4 seems to have no effect.
Am I reading this correct, that the box is simply dead after supsend ?
Fn/F4 are the keys you use to resume, right ?
Hmm, I have no idea how dynticks should influence the keyboard wakeup.
The box is somewhere in the guts of the BIOS at this point.
tglx
prev parent reply other threads:[~2007-02-25 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 23:38 2.6.21-rc1: T60 resume from suspend to RAM issues Michael S. Tsirkin
2007-02-23 10:09 ` Andrew Morton
2007-02-24 21:11 ` Michael S. Tsirkin
2007-02-27 10:14 ` Ingo Molnar
2007-02-27 10:28 ` Michael S. Tsirkin
2007-02-27 11:03 ` Ingo Molnar
[not found] ` <20070227110306.GE20927@elte.hu>
2007-02-27 11:33 ` Michael S. Tsirkin
2007-02-27 10:38 ` Pavel Machek
2007-02-25 9:03 ` Thomas Gleixner [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=1172394221.25076.359.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=bunk@stusta.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=mingo@redhat.com \
--cc=mst@mellanox.co.il \
--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