linux-kernel - Re: btusb autosuspend (was Re: Linux 2.6.38-rc6)

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: <Pine.LNX.4.44L0.1102240953320.2084-100000@iolanthe.rowland.org>
Date:	Thu, 24 Feb 2011 09:55:12 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Matthew Garrett <mjg59@...f.ucam.org>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Marcel Holtmann <marcel@...tmann.org>,
	"Gustavo F. Padovan" <padovan@...fusion.mobi>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Jeff Chua <jeff.chua.linux@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: btusb autosuspend (was Re: Linux 2.6.38-rc6)

On Thu, 24 Feb 2011, Matthew Garrett wrote:

> On Wed, Feb 23, 2011 at 04:25:23PM -0800, Linus Torvalds wrote:
> > Hmm. Is there any reason we shouldn't revert commit
> > 556ea928f78a390fe16ae584e6433dff304d3014 given the regression?
> 
> I think reverting makes sense at the moment. I haven't seen the reported 
> issues - I need to figure out if this is related to bus powered/self 
> powered devices, or what else is causing the difference.
> 
> > It apparently had problems before too, and caused autosuspend to be
> > disabled entirely, judging at least by
> > 
> >   https://bugzilla.redhat.com/show_bug.cgi?id=528744
> > 
> > but there's obviously the comment about "those should be fixed now".
> > Apparently there are more issues.
> 
> Right, we were autosuspending even when there were active connections. 
> Marcel told me that ought to be fixed and my testing seemed to agree...
> 
> > I have no idea whether this is a USB-level issue, or a driver-level
> > one. There are no comments about exactly what fixed the input device
> > issues. So I'm adding both BT and USB people to the discussion.
> 
> I'll try to get time to look at this this week. Marcel, any ideas?

Take a look at Bugzilla #26182.  I tried adding your address to the CC: 
list, but the only address I could find that Bugzilla would accept 
wasn't the same as the addresses you normally use.

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/