linux-kernel - Re: 2.6.21-rc1: T60 resume from suspend to RAM issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1172394221.25076.359.camel@localhost.localdomain>
Date:	Sun, 25 Feb 2007 10:03:41 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	"Michael S. Tsirkin" <mst@...lanox.co.il>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...sta.de>, pavel@...e.cz, linux-pm@...l.org,
	linux-acpi@...r.kernel.org, len.brown@...el.com, mingo@...hat.com
Subject: Re: 2.6.21-rc1: T60 resume from suspend to RAM issues

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/