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:	Thu, 18 Jun 2009 00:24:41 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Thomas Meyer <thomas@...3r.de>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Jiri Kosina <jkosina@...e.cz>,
	"Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: 2.6.30: suspend-to-ram, second s2r wakes up immediately

On Wednesday 17 June 2009, Thomas Meyer wrote:
> Sure. Rearranging the usb devices and removing some hubs makes the
> problem go away in most cases...

I see that you still have the Broadcom "Wireless RNDIS device" attached 
that was my initial suspect after looking through your boot log.

Does removing that device make the problem go away? Can you reproduce the 
problem at all without that device connected (during boot)?

Probably moving that device to a different controller than used for your 
keyboard and mouse will also get rid of the problem. Correct?

If removing that device does solve the problem, I would guess that without 
it you will also no longer have that "PME+" value in the output of lspci 
for the USB Controller it is connected to.

Hopefully someone else can then explain how/why that device forces the 
PME+ setting for the controller.

But I must also say that to me it seems rather fragile that in default 
configuration a random USB device can suddenly cause wakeups as result of 
a change caused by a totally different device.

Cheers,
FJP
--
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/