linux-kernel - Re: [linux-usb-devel] Error -71 on device descriptor read/all

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, 19 Jun 2007 15:04:36 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Paul Walmsley <paul@...yaka.com>
cc:	Oliver Neukum <oliver@...kum.org>,
	"Renato S. Yamane" <renatoyamane@...dic.com.br>,
	<linux-usb-devel@...ts.sourceforge.net>,
	Chuck Ebbert <cebbert@...hat.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] Error -71 on device descriptor read/all

On Tue, 19 Jun 2007, Paul Walmsley wrote:

> On Tue, 19 Jun 2007, Oliver Neukum wrote:
> 
> > Am Dienstag, 19. Juni 2007 schrieb Chuck Ebbert:
> >
> >> Try disabling CONFIG_USB_SUSPEND
> >>
> >> [usb developers: what are the drawbacks of doing this?]
> >
> > Increased power consumption.
> 
> speaking of CONFIG_USB_SUSPEND, I've encountered at least one device -- a 
> Canon EOS 5D camera -- that, after the bus suspends, must be powercycled 
> in order to return the camera's interrupt endpoints to a functional state. 
> How are these types of problems handled, currently?  Is this something for 
> a blacklist?

There are a few possible approaches.  One is indeed a blacklist, to 
prevent the camera from automatically being suspended.  Another is to 
prevent it by changing a device parameter in sysfs.

Note that neither of these will help if you do a suspend-to-RAM.  That 
suspends everything.

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/