Ubuntu

ehci_hcd module causes I/O errors in USB 2.0 devices

Reported by Al Buntu on 2007-02-28
804
This bug affects 111 people
Affects Status Importance Assigned to Milestone
Linux
Invalid
Medium
linux (Fedora)
Invalid
Unknown
linux (Ubuntu)
High
Unassigned
Declined for Gutsy by Henrik Nilsen Omma
Declined for Intrepid by Sarah Kowalik
Declined for Karmic by Steve Langasek
Hardy
High
Unassigned
Intrepid
High
Unassigned
Jaunty
High
Unassigned
linux-source-2.6.20 (Ubuntu)
High
Unassigned
Declined for Gutsy by Henrik Nilsen Omma
Declined for Intrepid by Sarah Kowalik
Declined for Karmic by Steve Langasek
Hardy
High
Unassigned
Intrepid
High
Unassigned
Jaunty
High
Unassigned
linux-source-2.6.22 (Baltix)
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
High
Unassigned
Declined for Gutsy by Henrik Nilsen Omma
Declined for Intrepid by Sarah Kowalik
Declined for Karmic by Steve Langasek
Hardy
High
Unassigned
Intrepid
Undecided
Unassigned
Jaunty
High
Unassigned

Bug Description

Certain USB devices do not work properly, or do not work at all, while the ehci_hcd module is loaded.

A solution is to unload the ehci_hcd module, which is loaded every time the computer starts, using the command 'sudo modprobe -r ehci_hcd'. This works fine but unfortunatly ehci-hcd is necessary for using USB 2.0, so you lose USB 2.0 features.
Another solution is to disable USB 2.0 through the BIOS setup.

With some devices it is possible to read files normally (ie. copy files from an USB pendrive to the computer), but the device disconnects abrubtly when you start writing data on the device. In some devices it fails after writing a certain amount of data, probably the size of the write cache.

Steps to reproduce:
1. Insert your USB 2.0 device (like a flash drive)
2. If the device is recognised and mounted properly try copying a file to it.
3. Comfirm with the 'dmesg' command that it isn't functioning properly. (I/O errors etc)
4. Remove the USB device
5. Unload ehci_hcd with 'sudo modprobe -r ehci_hcd'
6. Insert your USB device again.
7. Check that everything works. (copy some files, etc.)

A disproportionate number of individuals report Alcor chipsets in the problematic behavior. See:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/62
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/119
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/299
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/397
http://bugzilla.kernel.org/show_bug.cgi?id=ehci_hcd

Noted Workarounds:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/372

Al Buntu (biedermann2) wrote :

I have more informations:
My PC has 4 built-in USB-ports, 2 in front, 2 in the rear. They work without problems with the loaded ehci-modul. if I plug in an USB-stick there he will be recognized.
But:
When I additionally plug in an USB-hub the hub is recognized but after a few seconds my USB-stick is logged off. A message tells me: "Unsafe disc removal..." or something similar.
The same behavior I notice when there is only one usb-hub plugged in and I add a second usb-hub parallel to the first. The second hub "kills" the first.
If there are any additional questions don't hesitate to contact me.

description: updated
Al Buntu (biedermann2) wrote :

sometimes it's different:
the at first to the computer connected usb-stick works and the at second added usb-hub doesn't work. I think I get crazy...

Al Buntu (biedermann2) wrote :

I think there is something wrong with the ehci_hcd module. A few devices work allways and another few work sometimes, some of them only work when connected to the external usb-hub and other devices have to be connected directly to the usb-port iin the pc.
This is my concludion.

Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/DebuggingKernelProblems . Thanks in advance!

Al Buntu (biedermann2) wrote :

uname -a:
Linux schlumpf 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

Al Buntu (biedermann2) wrote :
Al Buntu (biedermann2) wrote :
Al Buntu (biedermann2) wrote :
pirast (pirast) wrote :

I can confirm this. Everything worked fine with 2.6.17 on Edgy, but with 2.6.20 on Feisty, I can not use any of my usb devices. After demodprobing ehci_hcd, I can use them again.

I have tried this with Feisty on three computers and the problem only appeard on one of them with the following hardware specs: Asus A7N8X-X with NForce 2 chipset.

This is the syslog output when plugging in a USB device having ehci_hcd *loaded* (thus, it does not work)

Mar 7 18:46:03 ubuntu kernel: [ 2809.360819] usb 3-3: device descriptor read/64, error -71
Mar 7 18:46:03 ubuntu kernel: [ 2809.576600] usb 3-3: new high speed USB device using ehci_hcd and address 10
Mar 7 18:46:03 ubuntu kernel: [ 2809.688487] usb 3-3: device descriptor read/64, error -71
Mar 7 18:46:04 ubuntu kernel: [ 2809.904277] usb 3-3: device descriptor read/64, error -71
Mar 7 18:46:04 ubuntu kernel: [ 2810.120055] usb 3-3: new high speed USB device using ehci_hcd and address 11
Mar 7 18:46:04 ubuntu kernel: [ 2810.527642] usb 3-3: device not accepting address 11, error -71
Mar 7 18:46:04 ubuntu kernel: [ 2810.639529] usb 3-3: new high speed USB device using ehci_hcd and address 12
Mar 7 18:46:05 ubuntu kernel: [ 2811.047116] usb 3-3: device not accepting address 12, error -71

(several times)

pirast (pirast) wrote :

Al Buntu, just noted that you also have a nforce 2 chipset.

Though, I will also attach my outputs.

pirast (pirast) wrote :
pirast (pirast) wrote :
pirast (pirast) wrote :
pirast (pirast) wrote :

I am going to change the title and the description slightly.

Al Buntu, which mainboard do you have?

description: updated

The guess about nforce2 to blame was wrong. In bug 87386 (now a duplicate of this one) someone has the same problem with a sis chipset.

Kyle McMartin (kyle) wrote :

Can one of you attach /proc/interrupts both with ehci_hcd loaded, and without?

Changed in linux-source-2.6.20:
assignee: nobody → kyle
status: Confirmed → Needs Info
pirast (pirast) wrote :
pirast (pirast) wrote :
Changed in linux-source-2.6.20:
status: Needs Info → Confirmed

My Mainboard:

Asus A7N8X-(X?)
with NForce 2

Greetings,

Al Buntu

Martin Jürgens schrieb:
> I am going to change the title and the description slightly.
>
> Al Buntu, which mainboard do you have?
>
> ** Summary changed:
>
> - my usb devices only work if I do "sudo modprobe -r ehci_hcd"
> + USB devices do not work with nforce 2 based motherboards
>
> ** Description changed:
>
> - the ehci_hcd is loaded every time the computer starts. This is normal
> - and necessary for using usb 2.0 highspeed. But not all usb compontents
> - work if this module has been loaded.
> + USB devices do not work with nforce 2 based motherboards.
> +
> + A solution is to unmodprobe ehci_hcd, which is loaded every time the
> + computer starts. This is normal and necessary for using usb 2.0
> + highspeed.
>
> ProblemType: Bug
> Date: Wed Feb 28 19:34:17 2007
> DistroRelease: Ubuntu 7.04
> Uname: Linux schlumpf 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
>
>

fixed in 2.6.20-10

Changed in linux-source-2.6.20:
status: Confirmed → Fix Released
pirast (pirast) wrote :

reappeard in 2.6.20-12-generic

Changed in linux-source-2.6.20:
assignee: kyle → ubuntu-kernel-team
status: Fix Released → Confirmed
pirast (pirast) on 2007-03-24
Changed in linux-source-2.6.20:
importance: Undecided → High
Jared Sutton (jpsutton) wrote :

I'm having the same issue here on a Thinkpad T40 and the Feisty Beta (2.6.20-12-generic). For now, I've put "modprobe -r ehci_hcd" in /etc/rc.local.

Mika Kukkonen (mikukkon) wrote :

I'm also having this same issue with current Feisty, i.e. none of my USB memory sticks are recognized after boot, but do work after doing "sudo modprobe -r ehci_hcd" (have not looked at the speed, though).

Doing "sudo lsusb" (without the modprobe workaround) causes following log:
usb 3-2: configuration #1 chosen from 1 choice
scsi6 : SCSI emulation for USB Mass Storage devices
usb 3-2: reset high speed USB device using ehci_hcd and address 17
usb 3-2: reset high speed USB device using ehci_hcd and address 17
usb 3-2: reset high speed USB device using ehci_hcd and address 17
usb 3-2: reset high speed USB device using ehci_hcd and address 17
usb 3-2: USB disconnect, address 17
usb 3-2: new high speed USB device using ehci_hcd and address 18
usb 3-2: new high speed USB device using ehci_hcd and address 19
usb 3-2: new high speed USB device using ehci_hcd and address 20
usb 3-2: new high speed USB device using ehci_hcd and address 21
usb 3-2: new high speed USB device using ehci_hcd and address 22

After the modprobe workaround, I get immediately this:
ehci_hcd 0000:00:02.2: remove, state 4
usb usb3: USB disconnect, address 1
usb 3-1: USB disconnect, address 2
ehci_hcd 0000:00:02.2: USB bus 3 deregistered
ACPI: PCI interrupt for device 0000:00:02.2 disabled
usb 1-1: new full speed USB device using ohci_hcd and address 3
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-2: new full speed USB device using ohci_hcd and address 4
usb 1-2: configuration #1 chosen from 1 choice
scsi8 : SCSI emulation for USB Mass Storage devices
scsi 8:0:0:0: Direct-Access USB 2.0 Flash Drive 1.00 PQ: 0 ANSI: 2
SCSI device sdd: 2058752 512-byte hdwr sectors (1054 MB)
sdd: Write Protect is off
device sdd: 2058752 512-byte hdwr sectors (1054 MB)
sdd: Write Protect is off
sdd: sdd1
sd 8:0:0:0: Attached scsi removable disk sdd
sd 8:0:0:0: Attached scsi generic sg3 type 0

And the device gets shown on desktop etc.

More info available on request.

pirast (pirast) wrote :

Works for me with 2.6.20-13-generic again. What about you?

Did a reboot, and it still does not work with 2.6.20-13-generic. Had
to do "sudo depmod -a" to get a workaround working, even. Same logs.

--MiKu

On 3/26/07, Martin Jürgens <email address hidden> wrote:
> Works for me with 2.6.20-13-generic again. What about you?
>
> --
> USB devices are not recognized when having ehci_hcd modprobed
> https://launchpad.net/bugs/88746
>

This page at ThinkWiki suggests that this may be a hardware issue (failing hardware): http://thinkwiki.org/wiki/Problem_with_USB_2.0

I'll test 2.6.20-13-generic to see if that solves it and I'll post back...

Mine is dual boot machine, and USB works fine under Windows...

--MiKu

On 4/5/07, Jared Sutton <email address hidden> wrote:
> This page at ThinkWiki suggests that this may be a hardware issue
> (failing hardware): http://thinkwiki.org/wiki/Problem_with_USB_2.0
>
> I'll test 2.6.20-13-generic to see if that solves it and I'll post
> back...
>
> --
> USB devices are not recognized when having ehci_hcd modprobed
> https://bugs.launchpad.net/bugs/88746
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Still the same issue with 2.6.20-13-generic here. :(

And with 2.6.20-14-generic too.

--MiKu

On 4/6/07, Jared Sutton <email address hidden> wrote:
> Still the same issue with 2.6.20-13-generic here. :(
>
> --
> USB devices are not recognized when having ehci_hcd modprobed
> https://bugs.launchpad.net/bugs/88746
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Same issues. The command:

modprobe -r ehci_hcd

"helped" somewhet.

Linux ewa 2.6.20-14-386 #2 Mon Apr 2 20:34:35 UTC 2007 i686 GNU/Linux

Asus A7N8X with NForce2 chipset

John Zero (johnzero) wrote :
stephg (stephg) wrote :

Same issue on Dapper.

My Lexar Card reader RW022 does not work anymore after kernel update on Dapper (Linux hyperion 2.6.15-28-386 #1 PREEMPT Thu Feb 1 15:51:56 UTC 2007 i686 GNU/Linux)

Works perfectly with 2.6.15-27

I also have an Asus A7N8X with NForce2 chipset

TheLimper (thelimper-rogers) wrote :

FYI:

I've noticed strange problems after upgrading to Feisty from Edgy with my USB devices on both my main PC and IBM R51 laptop.
Until I found this thread I couldn't figure out what was going on but I unmodprobing ehci_hcd restored things to how they functioned in Edgy.
I don't think this is bug is restricted to NFORCE 2 as my main PC is an NFORCE4 and the IBM R51 laptop is of course whatever they use.

The main thing I noticed on my NFORCE4 PC was during the boot my USB Creative labs LIVE! 24 External was being recognized but the 'blue light' was not powering on as was normal and I was getting strange sound problems.
After removing ehci_hd everything returned to normal.
I think something is definately off with the ehci_hcd module.

Just for the record, I tried the old_scheme_first trick recommend somewhere:

# echo Y > /sys/module/usbcore/parameters/old_scheme_first

and that did not help either :-(

--MiKu

Not much ideas, but some description of what the old_scheme_first thing is can be read here:
http://www.spinics.net/lists/usb/msg02644.html
Another (old) thread:
http://www.fedoraforum.org/forum/archive/index.php/t-30868.html

It seems strange that this might be an old bug that creeped back was not present in the previous Ubuntu version. (Or maybe an udev modfiication?)

I dug into kernel code a bit, and looked where does the
/var/log/kern.log messages come (at least in my case):

usb 3-2: new high speed USB device using ehci_hcd and address 11
usb 3-2: device descriptor read/64, error -71
usb 3-2: device descriptor read/64, error -71

As far I as I can read the code, that -71 is EPROTO and it gets set by
the following
code in usb_get_descriptor() in file drivers/usb/core/message.c :

  result = usb_control_msg(dev, usb_rcvctrlpipe(dev, 0),
    USB_REQ_GET_DESCRIPTOR, USB_DIR_IN,
    (type << 8) + index, 0, buf, size,
    USB_CTRL_GET_TIMEOUT);
  if (result == 0 || result == -EPIPE)
   continue;
  if (result > 1 && ((u8 *)buf)[1] != type) {
   result = -EPROTO;
   continue;
  }

Not much help there. Do others have the same error code/message in
their kern.log?

It seems that this bug is now present in the previous Ubuntu version.

As I said in my previous comment, my card reader that used to work with kernel 2.6.15-27 does not work anymore with 2.6.15-28 on Dapper.

I can make it work by unloading the ehci module. It really seems to be the same problem. The dmesg error messages are very similar too.

John Zero (johnzero) wrote :

Mika please read the attachments (dmesg.log), too.
Yes, everyone's having the same problem!

Based on the links I included, too, it seems that when the ehci_hcd module is not present, USB works in USB 1.1 mode. In USB 1.1 mode, the problem isn't there.
Of course, USB 1.1 is dead slow for many external devices.

I'm still not sure why it has worked in Dapper. Maybe the ehci driver worked well with NForce, but something has changed, breaking it? Or maybe it IS the 'old_scheme_first' that has changed. Not sure.

ingo (rum-topf) wrote :

Problem persists in Feisty

ingo@dicker:~$ lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 746 Host (rev 02)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
00:09.0 Mass storage controller: Promise Technology, Inc. PDC20375 (SATA150 TX2plus) (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)

Robert North (russetrob) wrote :

I too am having this problem in feisty, since install.
Current kernel: 2.6.20-15-generic.

Will attach log file, and hardware info later.

Alwin Garside (yogarine) on 2007-05-03
description: updated
Alwin Garside (yogarine) on 2007-05-28
description: updated
Changed in linux-source-2.6.22:
status: New → Invalid
assignee: nobody → ubuntu-kernel-team
importance: Undecided → High
status: New → Confirmed
Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
Changed in linux-source-2.6.22:
status: Confirmed → Triaged
Alwin Garside (yogarine) on 2007-10-30
description: updated
pirast (pirast) on 2007-11-02
Changed in linux-source-2.6.22:
status: Triaged → Fix Released
Alwin Garside (yogarine) on 2007-11-05
Changed in linux-source-2.6.22:
status: Fix Released → Confirmed
Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → High
status: New → Triaged
Changed in linux-source-2.6.22:
status: Confirmed → Won't Fix
Changed in linux:
status: Triaged → Incomplete
Changed in linux:
status: Incomplete → Triaged
Tim Gardner (timg-tpi) on 2008-02-13
Changed in linux-source-2.6.22:
status: Confirmed → Won't Fix
Changed in linux:
status: Triaged → Won't Fix
status: Triaged → Won't Fix
pirast (pirast) on 2008-05-30
Changed in linux:
status: Won't Fix → Confirmed
Changed in linux:
status: Unknown → Incomplete
Changed in linux:
status: Incomplete → Invalid
Changed in linux-source-2.6.20:
status: New → Won't Fix
Changed in linux:
status: Won't Fix → New
assignee: nobody → ubuntu-kernel-team
importance: Undecided → High
status: New → Confirmed
Changed in linux-source-2.6.22:
status: New → Won't Fix
Changed in linux-source-2.6.20:
importance: Undecided → High
Changed in linux:
status: Unknown → Invalid
description: updated
Changed in linux:
status: Confirmed → Fix Committed
status: New → Incomplete
Peter Hoeg (peterhoeg) on 2009-01-26
Changed in linux:
status: Fix Committed → Confirmed
TJ (tj) on 2009-03-20
Changed in linux:
status: Invalid → Unknown
Changed in linux (Ubuntu Jaunty):
assignee: nobody → intuitivenipple
status: Incomplete → In Progress
Changed in linux:
status: Unknown → Confirmed
Changed in linux (Ubuntu Jaunty):
status: In Progress → Fix Committed
Changed in linux (Ubuntu Jaunty):
status: Fix Committed → In Progress
Changed in linux:
status: Confirmed → Invalid
519 comments hidden view all 599 comments

Andreas Ermler píše v Pá 25. 09. 2009 v 21:59 +0000:
> Using Kernel Version 2.6.31 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.31/ did not solve the problem for me.
> I still get these:
> [ 631.112050] usb 1-8: reset high speed USB device using ehci_hcd and address 2
> ..and also a lot of other weird output that I haven't seen before, here is all of it:
> http://paste.ubuntu.com/278271/
>

For me, neither the new kernel doesn't work and my usb 2.0 card reader
keeps resetting with SDHC card in it (it works and worked fine with
MemoryStick.. I don't have any other card to test), although it works
fine in windows.

I have VIA VT8237 chipset.
--
Lukáš Chmela <email address hidden>
IRC: <email address hidden>, ICQ: 202077459
514D 3C69 8498 E400 0ACE 90F2 00E3 CACA A5BA ECC7

TJ (tj) on 2009-10-02
Changed in linux (Ubuntu Jaunty):
assignee: TJ (intuitivenipple) → nobody
status: In Progress → Confirmed

Bug still present in 2.6.31 kernel:

http://ubuntuforums.org/showpost.php?p=8102459&postcount=142

"I use ubuntu 9.10 on earlier kernels I had no problems after the upgrade but they were gone after sypalo

Linux bum-laptop 2.6.31-14-generic #46-Ubuntu SMP Tue Oct 13 16:47:59 UTC 2009 i686 GNU/Linux

[ 1237.548049] usb 1-2: new high speed USB device using ehci_hcd and address 3
[ 1237.696079] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 1239.357062] usb 1-2: new high speed USB device using ehci_hcd and address 4
[ 1239.490288] usb 1-2: configuration #1 chosen from 1 choice
[ 1239.586860] Initializing USB Mass Storage driver...
[ 1239.588588] scsi6 : SCSI emulation for USB Mass Storage devices
[ 1239.588863] usb-storage: device found at 4
[ 1239.588872] usb-storage: waiting for device to settle before scanning
[ 1239.588898] usbcore: registered new interface driver usb-storage
[ 1239.588908] USB Mass Storage support registered.
[ 1244.585060] usb-storage: device scan complete
[ 1251.245213] gvfsd-metadata[14843]: segfault at 8 ip 0804d2ea sp bff6edf0 error 4 in gvfsd-metadata[8048000+c000]
[ 1266.113051] usb 1-2: reset high speed USB device using ehci_hcd and address 4
[ 1266.436046] usb 1-2: reset high speed USB device using ehci_hcd and address 4
[ 1272.769054] usb 1-2: reset high speed USB device using ehci_hcd and address 4
[ 1273.105067] usb 1-2: reset high speed USB device using ehci_hcd and address 4
[ 1273.445079] usb 1-2: reset high speed USB device using ehci_hcd and address 4
[ 1273.644447] scsi 6:0:0:0: Device offlined - not ready after error recovery"

Stefano_PG (slot) wrote :

What is a "sypalo"?

and which chipset is this guy using?

Il 14/10/2009 18:16, Hated On Mostly ha scritto:
> Bug still present in 2.6.31 kernel:
>
> http://ubuntuforums.org/showpost.php?p=8102459&postcount=142
>
> "I use ubuntu 9.10 on earlier kernels I had no problems after the
> upgrade but they were gone after sypalo
>
> Linux bum-laptop 2.6.31-14-generic #46-Ubuntu SMP Tue Oct 13 16:47:59
> UTC 2009 i686 GNU/Linux
>
> [ 1237.548049] usb 1-2: new high speed USB device using ehci_hcd and address 3
> [ 1237.696079] hub 1-0:1.0: unable to enumerate USB device on port 2
> [ 1239.357062] usb 1-2: new high speed USB device using ehci_hcd and address 4
> [ 1239.490288] usb 1-2: configuration #1 chosen from 1 choice
> [ 1239.586860] Initializing USB Mass Storage driver...
> [ 1239.588588] scsi6 : SCSI emulation for USB Mass Storage devices
> [ 1239.588863] usb-storage: device found at 4
> [ 1239.588872] usb-storage: waiting for device to settle before scanning
> [ 1239.588898] usbcore: registered new interface driver usb-storage
> [ 1239.588908] USB Mass Storage support registered.
> [ 1244.585060] usb-storage: device scan complete
> [ 1251.245213] gvfsd-metadata[14843]: segfault at 8 ip 0804d2ea sp bff6edf0 error 4 in gvfsd-metadata[8048000+c000]
> [ 1266.113051] usb 1-2: reset high speed USB device using ehci_hcd and address 4
> [ 1266.436046] usb 1-2: reset high speed USB device using ehci_hcd and address 4
> [ 1272.769054] usb 1-2: reset high speed USB device using ehci_hcd and address 4
> [ 1273.105067] usb 1-2: reset high speed USB device using ehci_hcd and address 4
> [ 1273.445079] usb 1-2: reset high speed USB device using ehci_hcd and address 4
> [ 1273.644447] scsi 6:0:0:0: Device offlined - not ready after error recovery"
>
>

Somebody posted what they think is the root of the problem. Maybe others can test it out and give feedback. Very interesting post. CFQ (Completely Fair Queuing) might be the culprit. Links in the post are at the bottom.

http://ubuntuforums.org/showpost.php?p=8124807&postcount=144

I finally found the source of the problem, at least as far as my setup goes. Here's how I did it:

I got frustrated with the Ubuntu/Mint slow transfer rates and decided to check out Fedora. I installed it and ran it for a week or so. Fedora has excellent file transfer speeds, both to and from USB devices and SATA partitions. I copied the kernel config from my Fedora install.

I loaded Mint back into my system and compared the kernel config there with the one I pulled from Fedora. After compileing a half dozen kernels, Kernel I/O Scheduling turned out to be the answer.

By default, since I don't know when, Ubuntu started using CFQ (Completely Fair Queuing) for it's Kernel I/O Scheduling default, but there are a few other options available. Anticipatory and Deadline are the two that seem to work best.

I recompiled a new kernel with the Anticipatory I/O Scheduling and, lo and behold, I had my old 30MB/s USB transfer speeds back, and SATA performance was improves two or three times. (Though it's still not as fast a I think an intra-partition transfer should be on a single SATA hard drive, 10 or 12 megs a second is a lot better than two or three.) There's a noticeable drop in system performance while transfers are taking place, but, at least for me, it wasn't half as bad as it was with CFQ enabled.

Take all that with a grain of salt, though, because I've found forum posts from as far back as 2006 that show people enabling CFQ for the exact same reasons we'll want to disable it here.

Due to some unrelated experiments I was running with Xorg and the catastrophic fail that is the current Intel Video driver setup, I borked my install beyond repair and had to re-do it. Further research into the solution showed me that you can select a default I/O Scheduler at boot up by passing an option on to the kernel.

I found that by appending the string elevator=as to the end of the kernel parameters in /boot/grub/menu.lst, you can enable anticipatory I/O scheduling. The strings elevator=deadline and elevator=noop can be used as well, though I'm not so sure about their effects.

-------------
title Linux Mint 7 Gloria, kernel 2.6.28-15-generic
root (hd0,7)
 kernel /vmlinuz-2.6.28-15-generic root=/dev/sda6 ro quiet splash elevator=as
initrd /initrd.img-2.6.28-15-generic
quiet
-------------

It is also possible to change the I/O scheduler for certain devices without making it a system default, as can be found in these two blog posts.

I'd be interested in seeing if any of you get similar results by trying these solutions.

http://ubuntuforums.org/showthread.php?t=119546
http://www.cyberciti.biz/faq/linux-change-io-scheduler-for-harddisk/
http://planet.admon.org/howto/how-to-change-default-io-scheduler/

If people could post whether or not CFQ is enabled and whether they still have the slow usb problem that would be great info:

-------------
http://www.cyberciti.biz/faq/linux-change-io-scheduler-for-harddisk/

Task: View Current Disk scheduler

Assuming that your disk name /dev/sda, type in a terminal:

cat /sys/block/sda/queue/scheduler

--------

Copy and paste the output of the above command.

My system shows:

noop anticipatory [deadline] cfq

Which means my system (9.10 Karmic Koala beta with no updates) is using deadline by default and I am currently not experiencing the problem. I was experiencing the slow USB transfer speeds in 8.04 Hardy Heron and 8.10 Intrepid Ibex.

Stefano_PG (slot) wrote :

I tested a transfer from sda (ide) to sdb (Usb) of an iso (700mb).
The worst for me is the deadline, wich is about 0.5MB/s slower than cfq.
Anticipatory is about 0.7MB/s faster.
At the end I stay with cfq.

Il 19/10/2009 08:40, Hated On Mostly ha scritto:
> If people could post whether or not CFQ is enabled and whether they
> still have the slow usb problem that would be great info:
>
> -------------
> http://www.cyberciti.biz/faq/linux-change-io-scheduler-for-harddisk/
>
> Task: View Current Disk scheduler
>
> Assuming that your disk name /dev/sda, type in a terminal:
>
> cat /sys/block/sda/queue/scheduler
>
> --------
>
> Copy and paste the output of the above command.
>
> My system shows:
>
> noop anticipatory [deadline] cfq
>
> Which means my system (9.10 Karmic Koala beta with no updates) is using
> deadline by default and I am currently not experiencing the problem. I
> was experiencing the slow USB transfer speeds in 8.04 Hardy Heron and
> 8.10 Intrepid Ibex.
>
>

lvm (lvm-royal) wrote :

This problem is indeed alcor-specific, I changed internal card reader from the one based on alcor chipset to realtek and the problem is gone with no other software or hardware changes.

lisajo (ringwa) wrote :

I don't eally think this is only alcor-specific; please refer to:
http://ubuntuforums.org/showthread.php?p=8415658

Some details on what I tried; regardless, I'm still seeing
“usb 1-5: reset high speed USB device using ehci_hcd and address 3”

Same results with the following Kernels:
Linux ubuntu 2.6.32-5-generic (Lucid daily build 2009-11-30)
Linux ubuntu 2.6.31-50-generic (current one in Karmic)

Also same results trying different schedulers following the post from Hated on Mostly (noop, as and cfq on boot time with Kernel parameter and at runtime as described above).

The hardware involved:
2 external hdds, 3 USB – flash – disks; only difference is that the time to reset in dmesg varies.

The onboard – controller on my MB having all this trouble is:
USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396]

I do have no other hardware on USB – Bus; not even keyboard and mouse.

How I can get to work with USB:
Disabling USB2.0 – support in BIOS, or using the USB – ports on a USB – PCI – controller I added (because of this bug) with NEC – controller:
USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04)

I think USB2.0 – support should be absolutely reliable on modern computers with a current OS.
Please, review this bug.
I'm not a programming professional, but I'll try providing whatever information can help sorting this out.

Regards, lisajo

Peter B P (peterbp) wrote :

I've taken a new system into use today and can confirm that the bug is NOT unique to alcor USB chips.

The system log gets spammed with this on trying to read from USB 2.0 mass storage devices:

Dec 18 22:13:56 winter9 kernel: [ 2169.570023] usb 1-3: reset high speed USB device using ehci_hcd and address 2

I am also having severe problems with drive disconnects for 2,5" bus-powered USB units on the same system. (However the drives in question work flawlessly on an older Lenovo Portable system).

The Device Manager shows this to be the USB root hub:

82801JI (ICH10 Family) USB2 EHCI Controller #2
Intel Corporation (ASUSTeK Computer Inc.)
PCI (Peripheral Component Interconnect)

It is a USB controller on an ASUS motherboard; P5QL - EPU (Intel P-43 Chipset).

Hope this helps - this bug is unnerving.

filip (bandit-s-fw) wrote :

I think i also have this problem on my ext hdd (freecom XXX) when i try to run karmic from it. Tried the daily build (301209) of lucid but the same happens. The strange thing is that it works without a problem with karmic on my usb-stick (cruzer) on the same laptop.
lspci |grep USB
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)

markofealing (mark-ferns16) wrote :

I've also got this problem with a Freecom 160Gb USB drive Model (SSJABA), known as the Freecom Mobile Drive XXS, it is USB2.

If it is correctly detected by Karmic (also an issue with earlier versions of Ubuntu), it is very slow in reading and writing files (USB 1.1 Speed rather than USB2) when compared to a 80Gb Buffalo MiniStation USB disk I also have.

I've experienced problems on some NEC, VIA (all), and Alcor USB2 controller chipsets, although with Intel I've not had a problem but this is probably because my only Intel USB controller is USB1.1!

Dropping back to USB1.1 drivers fixes the problem but is unworkable with high capacity devices.

filip (bandit-s-fw) wrote :

markofealing: i misspelled my ext hdd it is also a Freecom Mobile Drive XXS like yours.

filip (bandit-s-fw) wrote :

I've installed jaunty on my Freecom Mobile Drive XXS to test. There it works everytime without problems but i see that my speeds are very low so i conclude that i must be using uhci. I hope that the dev's will look at this bug as with karmic and lucid the ehci is build in, so it is not possible to simply unload the module. Or am i wrong?

filip (bandit-s-fw) wrote :

i tried to update my lucid system that i run from my usb hdd (Freecom Mobile Drive XXS) and when updating the package acpi-support it tries to disable acpi powermanagement. that immediately triggers the well known errors: usb 1-4: device descriptor read/64, error .... for a couple of times and the system goes in read only mode and freezes. Maybe this can help solving the problem?

Pi (pi3832) wrote :

So, if I run:

dmesg | grep ehci*

I get:

[ 0.892115] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.892479] ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUB2] -> GSI 22 (level, low) -> IRQ 22
[ 0.892492] ehci_hcd 0000:00:02.1: setting latency timer to 64
[ 0.892496] ehci_hcd 0000:00:02.1: EHCI Host Controller
[ 0.892547] ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
[ 0.892571] ehci_hcd 0000:00:02.1: debug port 1
[ 0.892575] ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
[ 0.892593] ehci_hcd 0000:00:02.1: irq 22, io mem 0xfeafec00
[ 0.904018] ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00
[ 0.904459] ehci_hcd 0000:00:04.1: PCI INT B -> Link[UB12] -> GSI 21 (level, low) -> IRQ 21
[ 0.904467] ehci_hcd 0000:00:04.1: setting latency timer to 64
[ 0.904469] ehci_hcd 0000:00:04.1: EHCI Host Controller
[ 0.904503] ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 2
[ 0.904524] ehci_hcd 0000:00:04.1: debug port 1
[ 0.904528] ehci_hcd 0000:00:04.1: cache line size of 64 is not supported
[ 0.904544] ehci_hcd 0000:00:04.1: irq 21, io mem 0xfeafe800
[ 0.916016] ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00
[ 1.340016] usb 2-3: new high speed USB device using ehci_hcd and address 3
[ 4478.536017] usb 1-3: new high speed USB device using ehci_hcd and address 2
[ 6973.480021] usb 2-3: new high speed USB device using ehci_hcd and address 4
[ 6975.872018] usb 2-3: new high speed USB device using ehci_hcd and address 5
[10677.680020] usb 2-3: new high speed USB device using ehci_hcd and address 7
[12922.100581] usb 2-3: reset high speed USB device using ehci_hcd and address 7
[12958.113018] usb 2-3: reset high speed USB device using ehci_hcd and address 7
[12991.113026] usb 2-3: reset high speed USB device using ehci_hcd and address 7
[13030.113026] usb 2-3: reset high speed USB device using ehci_hcd and address 7
[...]
[16805.101018] usb 2-3: reset high speed USB device using ehci_hcd and address 7
[16840.101019] usb 2-3: reset high speed USB device using ehci_hcd and address 7
[16872.101024] usb 2-3: reset high speed USB device using ehci_hcd and address 7

But if I run:

modprobe -r ehci_hcd

I get:

FATAL: Module ehci_hcd not found.

Is my kernel (2.6.31-17) haunted by the ghost of this THREE YEAR OLD bug?

Also, changing 'scheduler' doesn't help. Changing 'max_sectors' doesn't help.

Andy Rabagliati (andyr) wrote :

@Pi - without more information, we can only cluck sympathetically.

Please attach the results of lspci -vvnn and lsusb - and tell us the result of trying the workarounds described above.

Newer kernels have unmodularised ehci_hcd so it cannot be removed.

You don't really want to remove it because USB transfers will slow to a crawl.

Lukáš Chmela (lukaschmela) wrote :

Andy Rabagliati píše v So 23. 01. 2010 v 11:08 +0000:
> @Pi - without more information, we can only cluck sympathetically.
>
> Please attach the results of lspci -vvnn and lsusb - and tell us the
> result of trying the workarounds described above.
>
> Newer kernels have unmodularised ehci_hcd so it cannot be removed.
>
> You don't really want to remove it because USB transfers will slow to a
> crawl.
>

Hi,
I am still experiencing this very ugly bug, although it affects only
"selected" devices that I have.
I think, it is related only to USB mass storage devices, as my camera
connected through USB and communicating through gphoto2 protocol works
fine when transferring data.

I have problem only with my USB memory card reader and my mobile phone
(when connected through usb mass storage mode) - those are the only USB
mass storage devices that I have.
These devices keeps resetting immediately after a specific amount data
has been transferred. For instance, my USB card reader is always reset
after every ~5 photo previews loaded in Nautilus and my mobile phone is
even not able to connect. It keeps turning its display off and on and in
system protocol still roll the same messages "usb 1-6: reset high speed
USB device using ehci_hcd and address 5" consequently.

I attach output of lspci -vvnn and lsusb on your request.

--
Lukáš Chmela <email address hidden>
IRC: <email address hidden>, ICQ: 202077459
514D 3C69 8498 E400 0ACE 90F2 00E3 CACA A5BA ECC7

filip (bandit-s-fw) wrote :
Download full text (5.6 KiB)

For my freecom XXS drive, i think also like mentioned in the devel-list that this is a very low level bug. If i boot from my disk it resets two times until i get to the desktop. But most of the times i doesn't get there. If i look in the logs the resets are not always on the same time. The resets already accured after disk recovery before the udev rules kick in.
If i connect the drive while running a full up to date lucid (on my usb-stick cruzer here no problem) i get this:

[ 626.470346] usb 1-5: new high speed USB device using ehci_hcd and address 5
Jan 27 19:17:11 lucidext kernel: [ 626.621195] usb 1-5: configuration #1 chosen from 1 choice
Jan 27 19:17:11 lucidext kernel: [ 626.622687] scsi7 : SCSI emulation for USB Mass Storage devices
Jan 27 19:17:16 lucidext kernel: [ 631.620682] scsi 7:0:0:0: Direct-Access Freecom Mobile Drive XXS PQ: 0 ANSI: 2 CCS
Jan 27 19:17:16 lucidext kernel: [ 631.621505] sd 7:0:0:0: Attached scsi generic sg3 type 0
Jan 27 19:17:16 lucidext kernel: [ 631.624982] sd 7:0:0:0: [sdc] 312581808 512-byte logical blocks: (160 GB/149 GiB)
Jan 27 19:17:16 lucidext kernel: [ 631.625774] sd 7:0:0:0: [sdc] Write Protect is off
Jan 27 19:17:16 lucidext kernel: [ 631.627691] sdc: sdc1 sdc2 sdc3 < sdc5 sdc6 > sdc4
Jan 27 19:17:16 lucidext kernel: [ 631.696161] sd 7:0:0:0: [sdc] Attached SCSI disk
Jan 27 19:17:23 lucidext kernel: [ 639.130061] usb 1-5: reset high speed USB device using ehci_hcd and address 5
Jan 27 19:17:31 lucidext kernel: [ 647.130060] usb 1-5: reset high speed USB device using ehci_hcd and address 5
Jan 27 19:18:02 lucidext kernel: [ 678.100318] usb 1-5: USB disconnect, address 5
Jan 27 19:18:02 lucidext kernel: [ 678.100343] sd 7:0:0:0: Device offlined - not ready after error recovery
Jan 27 19:18:02 lucidext kernel: [ 678.100361] sd 7:0:0:0: [sdc] Unhandled error code
Jan 27 19:18:02 lucidext kernel: [ 678.100365] sd 7:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
Jan 27 19:18:02 lucidext kernel: [ 678.100372] sd 7:0:0:0: [sdc] CDB: Read(10): 28 00 00 00 00 00 00 00 20 00
Jan 27 19:18:02 lucidext kernel: [ 678.100397] __ratelimit: 9 callbacks suppressed
Jan 27 19:18:02 lucidext kernel: [ 678.101560] sd 7:0:0:0: [sdc] Unhandled error code
Jan 27 19:18:02 lucidext kernel: [ 678.101564] sd 7:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jan 27 19:18:02 lucidext kernel: [ 678.101571] sd 7:0:0:0: [sdc] CDB: Read(10): 28 00 0d f8 ba 3f 00 00 02 00
Jan 27 19:18:03 lucidext kernel: [ 678.400059] usb 1-5: new high speed USB device using ehci_hcd and address 6
Jan 27 19:18:03 lucidext kernel: [ 678.551204] usb 1-5: configuration #1 chosen from 1 choice
Jan 27 19:18:03 lucidext kernel: [ 678.553600] scsi8 : SCSI emulation for USB Mass Storage devices
Jan 27 19:18:08 lucidext kernel: [ 683.592443] scsi 8:0:0:0: Direct-Access Freecom Mobile Drive XXS PQ: 0 ANSI: 2 CCS
Jan 27 19:18:08 lucidext kernel: [ 683.593290] sd 8:0:0:0: Attached scsi generic sg3 type 0
Jan 27 19:18:08 lucidext kernel: [ 683.664169] sd 8:0:0:0: [sdc] 312581808 512-byte logical blocks: (160 GB/149 GiB)
Jan 27 19:18:08 lucidext kernel: [ 683.664905] sd 8:0:0:0: [sdc] ...

Read more...

filip (bandit-s-fw) wrote :

I don't think it is a problem with the powersupply of the usb as my other externel hdd isn't usb-powered and i also get the same error messages.

AlfonSkunk (alfonskunk) wrote :

Since the last generic kernel in Karmic-Updates (2.6.31-20-57) everythings seems to go fine...

On changelog are some USB-related changes, but i can't determine which is the answer.

Debian-testing, kernel 2.6.32, has the same problem.

chipset USB: AMD SB600

some ports with USB 1.1 devices connected had ohci loaded, and the port with WDPassport HDD loads ehci without any error. Large transfers ok, without resets

I hadn't any "trick" of above, I made a new instalation.

Do you need any info?

draco (draco31-fr) wrote :

Hi,

On my case, almost all bugs related to usb are gone since kernel 2.6.32.9
Previously, with kernel 2.6.32.2, I still have major issues (no
detection / frequent usb reset / disconnection during transfer ...)
I don't try kernels between 2.632.2 and 2.6.32.9
Hope the fixes will be avaible in Lucid kernel or almost in proposed.

draco

AlfonSkunk a écrit :
> Since the last generic kernel in Karmic-Updates (2.6.31-20-57)
> everythings seems to go fine...
>
> On changelog are some USB-related changes, but i can't determine which
> is the answer.
>
> Debian-testing, kernel 2.6.32, has the same problem.
>
> chipset USB: AMD SB600
>
> some ports with USB 1.1 devices connected had ohci loaded, and the port
> with WDPassport HDD loads ehci without any error. Large transfers ok,
> without resets
>
> I hadn't any "trick" of above, I made a new instalation.
>
> Do you need any info?
>
>

battmanux (battmanu) wrote :

Hi AlfonSkunk,

I feel like having the same hardware than you, but the issu is not solved for me. That said, it seems to behave better than previous kernels. I will try to load 2.6.32.9+

Thanks for the update.

uname:
2.6.31-20-generic #57-Ubuntu SMP Mon Feb 8 09:05:19 UTC 2010 i686 GNU/Linux
lspic:
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
dmesg:
[ 108.209937] scsi 6:0:0:0: Direct-Access WD 2500BEV External 1.04 PQ: 0 ANSI: 4
[ 108.210653] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 108.215206] sd 6:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[ 108.216893] sd 6:0:0:0: [sdb] Write Protect is off
[ 108.216901] sd 6:0:0:0: [sdb] Mode Sense: 21 00 00 00
[ 108.216907] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 108.222198] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 108.222212] sdb:
[ 138.888961] usb 1-2.4: reset high speed USB device using ehci_hcd and address 7
[ 139.048916] sdb1
[ 169.877395] usb 1-2.4: reset high speed USB device using ehci_hcd and address 7
[ 169.971242] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 169.971257] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 200.876870] usb 1-2.4: reset high speed USB device using ehci_hcd and address 7
[ 231.876678] usb 1-2.4: reset high speed USB device using ehci_hcd and address 7
[ 262.889156] usb 1-2.4: reset high speed USB device using ehci_hcd and address 7
...

Ka-Hing Cheung (kahing) wrote :

00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
Linux struggle64 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux

With Lucid kernel, the situation improved compared to when I last tried in karmic. I can now copy bigger files without failing, but it's still failing in the couple hundred MBs range:

Mar 14 17:56:12 struggle64 kernel: [166687.122634] usb 2-5: reset high speed USB
 device using ehci_hcd and address 12
Mar 14 17:56:42 struggle64 kernel: [166717.710350] usb 2-5: reset high speed USB
 device using ehci_hcd and address 12
Mar 14 17:57:13 struggle64 kernel: [166748.293341] usb 2-5: reset high speed USB
 device using ehci_hcd and address 12
Mar 14 17:57:24 struggle64 kernel: [166758.831391] usb 2-5: reset high speed USB
 device using ehci_hcd and address 12
Mar 14 17:57:34 struggle64 kernel: [166769.252614] usb 2-5: USB disconnect, address 12
Mar 14 17:57:34 struggle64 kernel: [166769.252645] sd 15:0:0:0: Device offlined - not ready after error recovery
Mar 14 17:57:34 struggle64 kernel: [166769.252677] sd 15:0:0:0: [sdc] Unhandled error code
Mar 14 17:57:34 struggle64 kernel: [166769.252681] sd 15:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Mar 14 17:57:34 struggle64 kernel: [166769.252690] sd 15:0:0:0: [sdc] CDB: Write(10): 2a 00 00 00 01 e0 00 00 f0 00
Mar 14 17:57:34 struggle64 kernel: [166769.252725] lost page write due to I/O error on sdc

thomas f (wastedfluid-gmail) wrote :
Download full text (8.0 KiB)

I have the same problem as many users.

Computer: Acer Aspire 5700

Randomly, my usb 2.0 drive disconnects and gives me a:

I have to remount - when I do, it's only at usb 1.1 speed until I restart... a lot of the time, I just have to restart - only to wait one more day for this to happen again.

Other interesting notes: All devices connected via USB(I have a hub that has a mouse, keyboard, and cell phone charger attached) do not work after this said event. The harddrive has its own power hookup. However, they do have power as my mouse's laser is on.

This JUST started happening when I upgraded to Ubuntu 9.10.

van@lywex:~$ uname -a
Linux lywex 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC 2010 i686 GNU/Linux
van@lywex:~$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse
Bus 001 Device 005: ID 046d:c312 Logitech, Inc. DeLuxe 250 Keyboard
Bus 001 Device 003: ID 0402:5602 ALi Corp. Video Camera Controller
Bus 001 Device 002: ID 050d:0304 Belkin Components
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 1058:1100 Western Digital Technologies, Inc.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
van@lywex:~$

Mar 17 18:57:03 lywex kernel: [77088.124106] usb 1-7: reset high speed USB device using ehci_hcd and address 4
Mar 17 18:57:18 lywex kernel: [77103.299319] usb 1-7: device descriptor read/64, error -110
Mar 17 18:57:34 lywex kernel: [77118.548148] usb 1-7: device descriptor read/64, error -110
Mar 17 18:57:34 lywex kernel: [77118.764072] usb 1-7: reset high speed USB device using ehci_hcd and address 4
Mar 17 18:57:49 lywex kernel: [77133.912079] usb 1-7: device descriptor read/64, error -110
Mar 17 18:58:04 lywex kernel: [77149.164101] usb 1-7: device descriptor read/64, error -110
Mar 17 18:58:04 lywex kernel: [77149.380087] usb 1-7: reset high speed USB device using ehci_hcd and address 4
Mar 17 18:58:15 lywex kernel: [77159.812079] usb 1-7: device not accepting address 4, error -110
Mar 17 18:58:15 lywex kernel: [77159.924129] usb 1-7: reset high speed USB device using ehci_hcd and address 4
Mar 17 18:58:25 lywex kernel: [77170.356082] usb 1-7: device not accepting address 4, error -110
Mar 17 18:58:25 lywex kernel: [77170.356183] usb 1-7: USB disconnect, address 4
Mar 17 18:58:25 lywex kernel: [77170.356194] sd 2:0:0:0: Device offlined - not ready after error recovery
Mar 17 18:58:25 lywex kernel: [77170.356222] sd 2:0:0:0: [sdb] Unhandled error code
Mar 17 18:58:25 lywex kernel:...

Read more...

Hunk (enrique-garciasimon) wrote :
Download full text (3.6 KiB)

External USB drive working ok with Karmic (and with other windows computers and with a DVB recorder), but it does not work with lucid in the same computer.
I could give more information: it does not work never in lucid (2.6.32), but always in karmic (2.6.31)

Karmic (boot from DVD, now I have just lucid installed)

Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

[ 2474.890140] usb 2-1: new high speed USB device using ehci_hcd and address 5
[ 2475.042459] usb 2-1: configuration #1 chosen from 1 choice
[ 2475.049496] scsi8 : SCSI emulation for USB Mass Storage devices
[ 2475.049715] usb-storage: device found at 5
[ 2475.049720] usb-storage: waiting for device to settle before scanning
[ 2480.040382] usb-storage: device scan complete
[ 2480.041025] scsi 8:0:0:0: Direct-Access SAMSUNG HM500JI PQ: 0 ANSI: 2 CCS
[ 2480.041908] sd 8:0:0:0: Attached scsi generic sg3 type 0
[ 2480.055180] sd 8:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 2480.055914] sd 8:0:0:0: [sdc] Write Protect is off
[ 2480.055918] sd 8:0:0:0: [sdc] Mode Sense: 34 00 00 00
[ 2480.055922] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 2480.057412] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 2480.057418] sdc: sdc1
[ 2480.096328] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 2480.096339] sd 8:0:0:0: [sdc] Attached SCSI disk

Lucid (same disk, same usb connector, same cable ...)It does not work, I am wrinting from karmic, looking in /var/log/messages I see that. I think that dmesg shows other message about I/O error block 0, 1, ... to 7

Mar 18 21:25:47 enrique-laptop kernel: [ 0.000000] Linux version 2.6.32-16-generic (buildd@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-3ubuntu1) ) #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 (Ubuntu 2.6.32-16.25-generic)

Mar 18 20:30:46 enrique-laptop kernel: [ 491.690142] usb 2-2: new high speed USB device using ehci_hcd and address 4
Mar 18 20:30:46 enrique-laptop kernel: [ 491.842103] usb 2-2: configuration #1 chosen from 1 choice
Mar 18 20:30:46 enrique-laptop kernel: [ 491.851266] scsi7 : SCSI emulation for USB Mass Storage devices
Mar 18 20:30:51 enrique-laptop kernel: [ 496.851113] scsi 7:0:0:0: Direct-Access SAMSUNG HM500JI PQ: 0 ANSI: 2 CCS
Mar 18 20:30:51 enrique-laptop kernel: [ 496.854597] sd 7:0:0:0: Attached scsi generic sg2 type 0
Mar 18 20:30:51 enrique-laptop kernel: [ 496.855288] sd 7:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Mar 18 20:30:51 enrique-laptop kernel: [ 496.856029] sd 7:0:0:0: [sdb] Write Protect is off
Mar 18 20:30:51 enrique-laptop kernel: [ 496.857537] sdb: sdb1
Mar 18 20:30:51 enrique-laptop kernel: [ 496.863524] sd 7:0:0:0: [sdb] Attached SCSI disk
Mar 18 20:30:59 enrique-laptop kernel: [ 504.160133] usb 2-2: reset high speed USB device using ehci_hcd and address 4
Mar 18 20:31:08 enrique-laptop kernel: [ 513.160121] usb 2-2: reset high speed USB device using ehci_hcd and address 4
Mar 18 20:31:09 enrique-laptop kernel: [ 514.648447] sd 7:0:0:0: [sdb] Unhandled sense code
Mar 18 20:31:09 enrique-laptop kernel: [ 514.648457] sd 7:0:0:0: [sdb] ...

Read more...

Hunk (enrique-garciasimon) wrote :

Include the output of dmesg on lucid.
At least in my case It is not a chipset bug: it ALWAYS works in karmic, it NEVER works in lucid (same disk, same computer, same cable)
I am really interested in a solution in lucid: please ask for more info I could provide

2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux

[ 5290.361460] usb-storage: waiting for device to settle before scanning
[ 5295.360404] usb-storage: device scan complete
[ 5295.361003] scsi 6:0:0:0: Direct-Access SAMSUNG HM500JI PQ: 0 ANSI: 2 CCS
[ 5295.364829] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 5295.373050] sd 6:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 5295.373784] sd 6:0:0:0: [sdb] Write Protect is off
[ 5295.373791] sd 6:0:0:0: [sdb] Mode Sense: 34 00 00 00
[ 5295.373797] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 5295.375914] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 5295.375923] sdb: sdb1
[ 5295.399788] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 5295.399798] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 5303.160301] usb 2-1: reset high speed USB device using ehci_hcd and address 3
[ 5312.160077] usb 2-1: reset high speed USB device using ehci_hcd and address 3
[ 5313.629847] sd 6:0:0:0: [sdb] Unhandled sense code
[ 5313.629857] sd 6:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 5313.629866] sd 6:0:0:0: [sdb] Sense Key : Medium Error [current]
[ 5313.629875] sd 6:0:0:0: [sdb] Add. Sense: Unrecovered read error
[ 5313.629885] sd 6:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 01 00 00 08 00
[ 5313.629904] end_request: I/O error, dev sdb, sector 1
[ 5313.629914] Buffer I/O error on device sdb1, logical block 0
[ 5313.629925] Buffer I/O error on device sdb1, logical block 1
[ 5313.629931] Buffer I/O error on device sdb1, logical block 2
[ 5313.629936] Buffer I/O error on device sdb1, logical block 3
[ 5313.629942] Buffer I/O error on device sdb1, logical block 4
[ 5313.629947] Buffer I/O error on device sdb1, logical block 5
[ 5313.629953] Buffer I/O error on device sdb1, logical block 6
[ 5313.629958] Buffer I/O error on device sdb1, logical block 7

Recently received a similar message after upgrading my 10.04 Beta 1 with some nightly updates. Unfortunately it is my mouse and keyboard that are connected to via Bluetooth and USB which has meant they have been disabled. I have mouse/kb activity until about the time gdm launches at which point they become disabled. Removing the Logitech BT adapter from the USB slot prints this message:

btusb_bulk_complete: hci1 urb ffff88017fa30480 failed to resubmit
btusb_bulk_complete: hci1 urb ffff88017fa30000 failed to resubmit
btusb_send_frame: hci1 urb ffff8801813cb780 submission failed

Attempts to re-insert do not resolve the error and removal of the adapter adds more messages of a similar type to above.

At this time I cannot do anything else in my Lucid 10.04 and have had to file the bug from another platform.

Sergio Zanchetta (primes2h) wrote :

Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on 30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please feel free to report any other bugs you may find.
Thank you.

Changed in linux (Ubuntu Intrepid):
status: Confirmed → Won't Fix
Sergio Zanchetta (primes2h) wrote :

I've just realized I made a mistake, Intrepid Ibex 8.10 "will reach" EOL on 30 "APRIL" 2010.

Sorry for this.

Anyway, I think that one month doesn't make any difference now.

Ka-Hing Cheung (kahing) wrote :

This bug (which admittedly, may be multiple bugs affecting different chipsets) is still present in Lucid

Download full text (7.6 KiB)

As I remember but not exactly either "safely remove" or "umount" does not properly and safely remove the device even in previous ubuntu 64 and 32. I am not sure but I think that right click menu "umount" works but not "safely remove" (after that I had problems with mounting it in windows PC which I used to solve by using a LiveCD, opening the device to see the content, closing and restarting PC with windows)

I think that "safely remove" does not umounts properly the device.

Cannot reproduce the problem since it appears randomly.

this is from last unfortunate time:
I inserted the usb, (fat32), made some heavy copy, move etc.
After copy tried to delete some files but were not deleted ( right click menu "to trash" was dimmed).
I tried "safely remove" or "umount" from right click menu. (Do not remember for sure)
I removed usb after some seconds that ubuntu did nothing -but removed icon from desktop, tried it in some XP pro which found it as non formatted, retried some times in ubuntu. (removing it from one usb slot and inserting it in the other

ilias@fserver2:~$ uname -a
Linux fserver2 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux
from messages.log
...
May 24 19:03:05 fserver2 kernel: [36862.532225] usb 1-2: new high speed USB device using ehci_hcd and address 2
May 24 19:03:06 fserver2 kernel: [36862.684119] usb 1-2: configuration #1 chosen from 1 choice
May 24 19:03:06 fserver2 kernel: [36862.737500] Initializing USB Mass Storage driver...
May 24 19:03:06 fserver2 kernel: [36862.737625] scsi4 : SCSI emulation for USB Mass Storage devices
May 24 19:03:06 fserver2 kernel: [36862.737770] usbcore: registered new interface driver usb-storage
May 24 19:03:06 fserver2 kernel: [36862.737807] USB Mass Storage support registered.
May 24 19:03:11 fserver2 kernel: [36867.733222] scsi 4:0:0:0: Direct-Access A-DATA USB Flash Drive 0.00 PQ: 0 ANSI: 2
May 24 19:03:11 fserver2 kernel: [36867.733646] sd 4:0:0:0: Attached scsi generic sg4 type 0
May 24 19:03:11 fserver2 kernel: [36867.734848] sd 4:0:0:0: [sdd] 31588352 512-byte logical blocks: (16.1 GB/15.0 GiB)
May 24 19:03:11 fserver2 kernel: [36867.735468] sd 4:0:0:0: [sdd] Write Protect is off
May 24 19:03:11 fserver2 kernel: [36867.737958] sdd: sdd1
May 24 19:03:11 fserver2 kernel: [36868.065725] sd 4:0:0:0: [sdd] Attached SCSI removable disk
May 24 19:03:11 fserver2 kernel: [36868.490683] usb 1-2: reset high speed USB device using ehci_hcd and address 2
May 24 19:03:14 fserver2 kernel: [36871.379937] usb 1-2: reset high speed USB device using ehci_hcd and address 2
.... hundreds of the same msg
May 24 19:05:20 fserver2 kernel: [36996.847299] usb 1-2: reset high speed USB device using ehci_hcd and address 2
May 24 19:05:41 fserver2 pulseaudio[1558]: ratelimit.c: 364 events suppressed
May 24 19:05:50 fserver2 kernel: [37027.520881] usb 1-2: reset high speed USB device using ehci_hcd and address 2
.... hundreds of the same msg
May 24 19:31:21 fserver2 kernel: [38557.991283] usb 1-2: reset high speed USB device using ehci_hcd and address 2
May 24 19:33:46 fserver2 kernel: [38702.933288] npviewer.bin[7782]: segfault at ff999ea8 ip 00000000ff999ea8 sp 00000000ffe27f...

Read more...

Jeremy Foshee (jeremyfoshee) wrote :

Folks,
     This bug, due in very large part to the huge amount of comments it has received, is no longer useful at all from a bug fix standpoint. As such, I am marking this bug Won't Fix.

If you are affected by a bug that has been marked as a duplicate of this one, please unmark the duplicate. This is in keeping with the new Ubuntu Kernel Team policy of treating each bug as a separate issue even if the hardware and the error is exactly the same. The reasoning for this is that fixes for some bugs that appear to be duplicates do not always fix all possible duplicates and we have found that most of the cases were not reported as bugs with all debug information attached.

For those affected by this who have not filed a bug, please do so now including all relevant debugging and logging so that we can begin the process of looking into your issue on its merit.

For those wishing to simply discuss the issue, please see the forum for relevant threads on the subject while keeping in mind that the Ubuntu Kernel Team does not frequent the forum so you should take any advice you are given for what it is, advice only.

Thanks!

~JFo

Changed in linux (Ubuntu):
assignee: TJ (intuitivenipple) → nobody
status: In Progress → Won't Fix
Changed in linux (Ubuntu Hardy):
status: Confirmed → Won't Fix
Changed in linux (Ubuntu Jaunty):
status: Confirmed → Won't Fix
Andy Rabagliati (andyr) wrote :

> This bug, due in very large part to the huge amount of comments it has received, is no longer useful at all from a bug fix standpoint. As such, I am marking this bug Won't Fix.

There are plenty of detailed logs in the comments (including my own) that are presented to help fix this long-standing bug.

I think it is a cop-out to say that all the *other* comments invalidate this bug.

I request that the bug be re-opened.

By all means delete all other non-useful comments.

Jeremy Foshee (jeremyfoshee) wrote :

Andy,
    I regret that you feel this to be some sort of 'cop out', however, I am acting in my official capacity as the Kernel Bug Supervisor. It appears you are relatively unfamiliar with Launchpad as there is no facility for deleting non-useful comments. Even if there were, it would be a misuse of time to read through the 590 comments in this bug to determine what was of use. It is the Kernel Teams policy to close such bugs and have affected reporters open new bugs. This is the reason for my subsequent closing of this bug. I have asked for, and frankly hope for additions to Launchpad in the future that i anticipate will help in situations like this. Those are not yet reality. Your remark that there are plenty of detailed logs attached also illustrates a part of the problem. Were this bug to reach one of my Engineers, it would be impossible to wade through all of the logs to 1) verify the issue and 2) determine a fix.

I also think you may be suffering from a mis-perception of the Ubuntu Kernel Team. This team is focused on providing relevant stable updates from upstream in a versioned distribution of Ubuntu released every six months. That said, the team's focus is not on bug resolution but rather on insuring that the relevant and needed patches to address a majority of hardware are included upon release. Any issue that needs to be addressed in a different manner needs to be brought to the attention of the Linux Kernel maintainers via bugzilla.kernel.org.

I hope you find this useful.

Thanks!

~JFo

johnnyb0y (ubuntu64) wrote :

I'm STILL affected by this bug, on different media (External HDD powered USB2 drives, and flash drives). This is on Lucid Lynx.

TO summarise, I think the frustrations felt by the user community are valid. Looking at the top of this thread reveals the following rather pertinent information and it certainly gives the impression that nothing is being done about it. To inject a little humour, it makes you sound like Kevin The Teenager ;-) Can't fix, won't fix.

Won't Fix
Declined for Gutsy by Henrik Nilsen Omma
Declined for Intrepid by Sarah Hobbs
Declined for Karmic by Steve Langasek
   Hardy
Won't Fix
   Intrepid
Won't Fix
   Jaunty
Won't Fix
Declined for Gutsy by Henrik Nilsen Omma
Declined for Intrepid by Sarah Hobbs
Declined for Karmic by Steve Langasek
   Hardy
Won't Fix
   Intrepid
   Jaunty
Won't Fix
Declined for Gutsy by Henrik Nilsen Omma
Declined for Intrepid by Sarah Hobbs
Declined for Karmic by Steve Langasek
   Hardy
Won't Fix
   Intrepid
Won't Fix

I look forward to the day when this bug is finally fixed, and thank you guys in advance for the effort.

Regards

John Goodwin.

Changed in linux:
importance: Unknown → Medium
Ralph (kesselr1) wrote :
Download full text (74.1 KiB)

Page 1 (Scheduler not running?):
{'cups_connection_failure': False}
Page 2 (Choose printer):
{'cups_dest': <cups.Dest Lexmark_3600-4600_Series>,
 'cups_instance': None,

Dump of lusb-v:

Bus 002 Device 005: ID 046d:c044 Logitech, Inc. LX3 Optical Mouse
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x046d Logitech, Inc.
  idProduct 0xc044 LX3 Optical Mouse
  bcdDevice 27.20
  iManufacturer 1 Logitech
  iProduct 2 USB-PS/2 Optical Mouse
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 34
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 98mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 3 Human Interface Device
      bInterfaceSubClass 1 Boot Interface Subclass
      bInterfaceProtocol 2 Mouse
      iInterface 0
        HID Device Descriptor:
          bLength 9
          bDescriptorType 33
          bcdHID 1.10
          bCountryCode 0 Not supported
          bNumDescriptors 1
          bDescriptorType 34 Report
          wDescriptorLength 59
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0005 1x 5 bytes
        bInterval 10
Device Status: 0x0000
  (Bus Powered)

Bus 002 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize0 64
  idVendor 0x05e3 Genesys Logic, Inc.
  idProduct 0x0608 USB-2.0 4-Port HUB
  bcdDevice 77.63
  iManufacturer 0
  iProduct 1 USB2.0 Hub
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 10...

I'm seeing the same thing in 13.04 w/ Samsung Galaxy Note. It used to work fine, but after upgrading from 12.10->13.04 and from ICS->JB, this device is unusable from Ubuntu. Dual boot to Windows and it works fine.

Linux hydra 3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:22:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Attached file is log from plugging device in for just a moment. If I leave it connected, I will get a never-ending stream of popups that look like "Unable to open MTP device '[usb:003,021]'" with 021 rotating between all numbers up to 127 and then starting over. I believe that is caused by the constant flow of:

Jun 8 07:11:52 hydra kernel: [ 525.282788] usb 3-4: reset high-speed USB device number 3 using ehci-pci
Jun 8 07:11:52 hydra kernel: [ 525.362789] usb 3-4: USB disconnect, device number 3

This has started happening on my other Ubuntu box now. Turning off 'usb debugging' makes the problem go away - of course that means no longer using ADB.

Narcis Garcia (narcisgarcia) wrote :

I had this problem with Ubuntu-Gnome 13.04 on a HP Pavilion g6 laptop. Some USB ports didn't work (as if they didn't exist).
My workaround has been to add "nomodeset" parameter to kernel boot parameters.

I just switched from the Samsung Galaxy Note to the Google Edition of HTC One and do not have this problem with the new device. Maybe Samsung specific?

Displaying first 40 and last 40 comments. View all 599 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.