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:	Tue, 16 Jun 2009 14:50:48 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Thomas Meyer <thomas@...3r.de>
cc:	Jiri Kosina <jkosina@...e.cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
	Frans Pop <elendil@...net.nl>, <linux-kernel@...r.kernel.org>,
	<linux-usb@...r.kernel.org>
Subject: Re: 2.6.30: suspend-to-ram, second s2r wakes up immediately

On Tue, 16 Jun 2009, Thomas Meyer wrote:

> Yes. These patches make usbmon stop abending.
> 
> Successful suspend -> stay in S3 -> resume cylce:

Unfortunately this log is uninterpretable, thanks largely to the two 
mass-storage devices at addresses 9 and 10.  I can't tell what they
are because they don't appear to be listed in the dmesg log you
posted.

The device at address 10 isn't working at all.  It apparently has 4
LUNs but it replies to all commands for all LUNs with an error code
saying that the LUN isn't supported.

The device at address 9 is working, but its I/O clutters up the log.

There's also something at address 4; perhaps an HID device, I can't
tell.

Can you run the test again, this time with no extraneous USB devices 
plugged in?  (That includes hubs.)  And before starting the test, 
collect the contents of /sys/kernel/debug/usb/devices (you'll probably 
have to mount /sys/kernel/debug first).

Alan Stern

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