linux-kernel - Re: [34-stable regression] USB delay init quirk causes device events loss

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: <20100913170656.GA9122@suse.de>
Date:	Mon, 13 Sep 2010 10:06:56 -0700
From:	Greg KH <gregkh@...e.de>
To:	Jiri Slaby <jslaby@...e.cz>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Phil Dibowitz <phil@...m.com>, stable@...nel.org,
	USB list <linux-usb@...r.kernel.org>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: [34-stable regression] USB delay init quirk causes device
 events loss

On Mon, Sep 13, 2010 at 07:03:07PM +0200, Jiri Slaby wrote:
> On 09/13/2010 06:24 PM, Alan Stern wrote:
> > Jiri, as a workaround for people using the current 3.6.34.stable, you
> > can ask them to do:
> > 
> > 	echo on >/sys/bus/usb/devices/.../power/level
> > 
> > with the "..." filled in appropriately.
> 
> Yeah, the people are using that already. (Actually, they attached a udev
> script to do that automatically.) Or usbcore.autosuspend=-1 is an easier
> workaround (but disables autosuspend completely, indeed).

I've now released 2.6.34.7 with this patch reverted so all should be
good now.

thanks,

greg k-h
--
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/