linux-kernel - Re: 2.6.30: suspend-to-ram, second s2r wakes up immediately

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]

Date:	Sun, 14 Jun 2009 18:28:11 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Thomas Meyer <thomas@...3r.de>
Cc:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: 2.6.30: suspend-to-ram, second s2r wakes up immediately

On Sunday 14 June 2009, Thomas Meyer wrote:
> Hello.
> 
> After a cold start of the computer, the first suspend-to-ram works as it
> should and everything is fine.
> 
> But after waking up again, the second suspend-to-ram (in a row) seems to
> work, but the computer wakes up immediately (i.e. it doesn't stay in
> S3)!
> 
> Now the strange part: after re-plugging my 4-port usb hub, the computer
> (in a third suspend-to-ram try) enters S3 without waking up immediately
> again.
> 
> Strange, hmm?

So, it looks like there's a device that generates a wake-up request after the
second suspend automatically.

Can you send the output of lspci from the box?

Rafael
--
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/