public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Phil Dibowitz <phil@ipom.com>,
	stable@kernel.org, USB list <linux-usb@vger.kernel.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [34-stable regression] USB delay init quirk causes device events loss
Date: Mon, 13 Sep 2010 10:06:56 -0700	[thread overview]
Message-ID: <20100913170656.GA9122@suse.de> (raw)
In-Reply-To: <4C8E594B.6080100@suse.cz>

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

  reply	other threads:[~2010-09-13 17:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 11:18 [34-stable regression] USB delay init quirk causes device events loss Jiri Slaby
2010-09-13 14:16 ` Alan Stern
2010-09-13 14:23   ` Jiri Slaby
2010-09-13 14:48     ` Alan Stern
2010-09-13 14:59       ` Jiri Slaby
2010-09-13 15:37         ` Alan Stern
2010-09-13 15:56           ` Greg KH
2010-09-13 16:02             ` Phil Dibowitz
2010-09-13 16:24               ` Alan Stern
2010-09-13 17:03                 ` Jiri Slaby
2010-09-13 17:06                   ` Greg KH [this message]
2010-09-14 12:03           ` Oliver Neukum
2010-09-14 14:03             ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100913170656.GA9122@suse.de \
    --to=gregkh@suse.de \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=phil@ipom.com \
    --cc=stable@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox