[lkml]   [2011]   [Feb]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux 2.6.38-rc6
2011/2/22 Linus Torvalds <>:
> And for the people who actually reported the regressions (or didn't,
> but have found new ones) - please do update the status of the
> regression. Some of them I'm really feel a lot more happy about if
> they had a note that "yes, I tested with -rc6, and the problem is
> still there". We've fixed a fair number of problems, so it's always
> good to have regression reporters ping us with something like "hey,
> I'm still here, and you may have fixed all those other things, but you
> didn't fix my issue".

I just encountered this reported bug using Bluetooth Intermec scanners
and discovered that the recent kernel has the same problem as reported
below. ... the bluetooth
devices would just stop responding after a while.

[ 4533.361959] btusb 8-1:1.0: no reset_resume for driver btusb?
[ 4533.361964] btusb 8-1:1.1: no reset_resume for driver btusb?

It seems to that Fedora doesn't feel this is a big problem, but for
production systems, it's a big deal as the scanners can't connect to
the server.

Seems to relate to this commit. The workabout is to set
usbcore.autosuspend=-1 as command line options, but as this is not
working as intended, then it should be either be fixed or reverted.


commit 556ea928f78a390fe16ae584e6433dff304d3014
Author: Matthew Garrett <>
Date: Thu Sep 16 13:58:15 2010 -0400

Bluetooth: Enable USB autosuspend by default on btusb

We've done this for a while in Fedora without any obvious problems other
than some interaction with input devices. Those should be fixed now, so
let's try this in mainline.

Signed-off-by: Matthew Garrett <>
Acked-by: Marcel Holtmann <>
Signed-off-by: Gustavo F. Padovan <>

 \ /
  Last update: 2011-02-23 10:45    [W:0.121 / U:1.172 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site