USB device intermittently disconnects after upgrading to feisty

Bug #110806 reported by Ashish Kulkarni on 2007-04-28
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
linux-source-2.6.20 (Ubuntu)

Bug Description

Binary package hint: linux-source-2.6.20

I have a REB 1100 device. After upgrading to feisty, it doesn't work properly. When I try to access it via rebcomm, it tells me that it is not on the device bus. When I look at the dmesg, it shows that it has been disconnected and reconnected (although it was never physically disconnected.

Ashish Kulkarni (ashkulz) wrote :
Ashish Kulkarni (ashkulz) wrote :
Ashish Kulkarni (ashkulz) wrote :
Ashish Kulkarni (ashkulz) wrote :

Binary Package: linux-image-2.6.20-15-generic

Ashish Kulkarni (ashkulz) wrote :

Okay, I did some googling and found the problem:

The problem seems to be the kernel config CONFIG_USB_SUSPEND=y

Apparently, this is a known problem upstream.

Ashish Kulkarni (ashkulz) wrote :

See for more details.

I can confirm that if I try to access it within 2 seconds of it being connected, it works. After two seconds, the USB_SUSPEND functionality causes it to hang up and reconnect.

Dean Loros (autocrosser) wrote :

When you look at Bug# 85488 (and other links)--this problem has been known for about 2 months. The common thought is that libusb needs to be reworked to work with the CONFIG_USB_SUSPEND kernel option. The more bug reports about this, the better.

Ashish Kulkarni (ashkulz) wrote :

Ok, I rebuilt the kernel on AMD64 without USB_SUSPEND, and everything works OK (mine is not a scanner problem, but another device altogether -- see bug #110806). If someone wants it, I will post it.

Of course, as I didn't build the linux-restricted-modules package (which requires 150MB of source download!!) my nVidia driver stopped working, which is OK as I can live with the open source driver.

If someone DOES want that, you can follow the instructions at

Mshillin (mshillinger) wrote :

I have and REB 1100 and a Thinkpad T60. I am running Fiesty with kernel 2.6.20-16

Using the scanbuttond utility seems to fix the problem for me.


Running 'scanbuttond -f -p 1000 -r 10000' prior to using rebcomm commands seems to work around the issue.

Hope it helps...


Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers