linux-kernel - Re: usb autosuspend is history after S2R (also on 2.6.31; UVC?)

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: <200909152148.29662.oliver@neukum.org>
Date:	Tue, 15 Sep 2009 21:48:28 +0200
From:	Oliver Neukum <oliver@...kum.org>
To:	Andreas Mohr <andi@...as.de>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	"Greg Kroah-Hartman" <gregkh@...e.de>, laurent.pinchart@...net.be,
	Matthew Garrett <mjg59@...f.ucam.org>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: usb autosuspend is history after S2R (also on 2.6.31; UVC?)

Am Dienstag, 15. September 2009 20:51:45 schrieb Andreas Mohr:

> So, does the uvc driver need a bit of handholding here?
> It likely shouldn't simply forget about its autosuspend status after
> resume...

Can you please provide what you get when you read the "level" file
of the device's power directory?

Secondly, please verify, that it works before the STR cycle and post
a syslog of a suspend/resume cycle with CONFIG_USB_DEBUG and
only this device attached if possible. Thirdly, please verify that only
uvc is affected.

> Or would Matthew's uvc autosuspend patch
> http://osdir.com/ml/fedora-extras-commits/2009-07/msg06079.html
> help here?

Please test it. It shouldn't work, but if it works there's a fundamental
flaw.

	Regards
		Oliver

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