external USB hard drive disconnects

[Steve Conklin]

This is a new external drive enclosure.

I can easily reproduce this:

Plug in the usb cable and power up the drive. System log shows:

Mar 27 11:05:07 XPS-1 kernel: [ 7259.584108] usb 2-2: new high speed USB device using ehci_hcd and address 7
Mar 27 11:05:07 XPS-1 kernel: [ 7259.720027] usb 2-2: configuration #1 chosen from 1 choice
Mar 27 11:05:07 XPS-1 kernel: [ 7259.757608] Initializing USB Mass Storage driver...
Mar 27 11:05:07 XPS-1 kernel: [ 7259.762530] scsi5 : SCSI emulation for USB Mass Storage devices
Mar 27 11:05:07 XPS-1 kernel: [ 7259.768158] usbcore: registered new interface driver usb-storage
Mar 27 11:05:07 XPS-1 kernel: [ 7259.768167] USB Mass Storage support registered.
Mar 27 11:05:12 XPS-1 kernel: [ 7264.769258] scsi 5:0:0:0: Direct-Access WDC WD16 00JB-75GVA0 08.0 PQ: 0 ANSI: 0
Mar 27 11:05:12 XPS-1 kernel: [ 7264.773347] sd 5:0:0:0: [sdb] 312499999 512-byte hardware sectors: (159 GB/149 GiB)
Mar 27 11:05:12 XPS-1 kernel: [ 7264.793936] sd 5:0:0:0: [sdb] Write Protect is off
Mar 27 11:05:12 XPS-1 kernel: [ 7264.801920] sd 5:0:0:0: [sdb] 312499999 512-byte hardware sectors: (159 GB/149 GiB)
Mar 27 11:05:12 XPS-1 kernel: [ 7264.804738] sd 5:0:0:0: [sdb] Write Protect is off
Mar 27 11:05:12 XPS-1 kernel: [ 7264.804760] sdb: sdb1
Mar 27 11:05:12 XPS-1 kernel: [ 7264.837230] sd 5:0:0:0: [sdb] Attached SCSI disk
Mar 27 11:05:12 XPS-1 kernel: [ 7264.837377] sd 5:0:0:0: Attached scsi generic sg2 type 0
Mar 27 11:05:13 XPS-1 kernel: [ 7265.513967] kjournald starting. Commit interval 5 seconds
Mar 27 11:05:13 XPS-1 kernel: [ 7265.513995] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Mar 27 11:05:13 XPS-1 kernel: [ 7265.515031] EXT3 FS on sdb1, internal journal
Mar 27 11:05:13 XPS-1 kernel: [ 7265.515040] EXT3-fs: recovery complete.
Mar 27 11:05:13 XPS-1 kernel: [ 7265.522316] EXT3-fs: mounted filesystem with ordered data mode.

Now if I do anything that causes reads from the drive (in this case "du -sh /media/disk", I get the following in the log:

Mar 27 11:05:48 XPS-1 kernel: [ 7300.911188] usb 2-2: reset high speed USB device using ehci_hcd and address 7
Mar 27 11:05:49 XPS-1 kernel: [ 7301.173948] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Mar 27 11:05:49 XPS-1 kernel: [ 7301.174001] usb 2-2: USB disconnect, address 7
Mar 27 11:05:49 XPS-1 kernel: [ 7301.174266] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Mar 27 11:05:49 XPS-1 kernel: [ 7301.174448] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Mar 27 11:05:49 XPS-1 kernel: [ 7301.174617] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Mar 27 11:05:49 XPS-1 kernel: [ 7301.174776] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Mar 27 11:05:49 XPS-1 kernel: [ 7301.174956] lost page write due to I/O error on sdb1
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175588] ------------[ cut here ]------------
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175594] WARNING: at /build/buildd/linux-2.6.28/fs/buffer.c:1186 mark_buffer_dirty+0x7d/0xa0()
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175599] Modules linked in: usb_storage aes_i586 aes_generic xt_limit xt_tcpudp ipt_LOG ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp xt_state i915 drm binfmt_misc ppdev bnep bridge stp kvm_intel kvm kqemu input_polldev joydev sbp2 lp parport iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle iptable_filter ip_tables x_tables snd_hda_intel arc4 ecb snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss iwlagn iwlcore snd_seq_midi snd_rawmidi snd_seq_midi_event uvcvideo snd_seq snd_timer snd_seq_device led_class compat_ioctl32 videodev hid_dell snd psmouse mac80211 soundcore intel_agp usbhid serio_raw agpgart snd_page_alloc v4l1_compat video cfg80211 sdhci_pci sdhci iTCO_wdt iTCO_vendor_support output dcdbas ohci1394 ieee1394 tg3 fbcon tileblit font bitblit softcursor [last unloaded: pcspkr]
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175756] Pid: 14093, comm: du Not tainted 2.6.28-11-generic #37-Ubuntu
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175761] Call Trace:
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175771] [<c0500ae1>] ? printk+0x18/0x1f
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175779] [<c0139ad4>] warn_on_slowpath+0x54/0x80
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175788] [<c033d600>] ? vt_console_print+0x1f0/0x320
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175797] [<c0502b68>] ? __lock_text_start+0x8/0x20
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175804] [<c033d640>] ? vt_console_print+0x230/0x320
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175812] [<c02cbbbb>] ? string+0x2b/0xe0
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175819] [<c033d410>] ? vt_console_print+0x0/0x320
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175827] [<c013a2a9>] ? release_console_sem+0x1c9/0x200
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175836] [<c01dd9fd>] mark_buffer_dirty+0x7d/0xa0
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175844] [<c0219e36>] ext3_commit_super+0x46/0x70
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175852] [<c021c138>] ext3_handle_error+0x48/0xb0
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175858] [<c0500ae1>] ? printk+0x18/0x1f
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175865] [<c021c261>] ext3_error+0x51/0x60
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175872] [<c0212f06>] __ext3_get_inode_loc+0x296/0x300
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175881] [<c01cfea7>] ? get_new_inode_fast+0xe7/0x120
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175888] [<c01d0ae3>] ? iget_locked+0x53/0x60
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175894] [<c0212fc5>] ext3_iget+0x55/0x3d0
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175903] [<c01ccb15>] ? d_rehash+0x45/0x60
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175909] [<c02187e1>] ext3_lookup+0x81/0xd0
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175916] [<c0502d08>] ? _spin_lock+0x8/0x10
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175923] [<c01ce767>] ? d_alloc+0x137/0x190
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175931] [<c01c6ac7>] real_lookup+0xa7/0x110
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175938] [<c01c6bb5>] do_lookup+0x85/0xc0
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175945] [<c01c7125>] __link_path_walk+0x535/0xb30
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175953] [<c01c7b74>] path_walk+0x54/0xb0
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175961] [<c01c7d0e>] do_path_lookup+0xae/0x190
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175968] [<c01c894a>] user_path_at+0x4a/0x80
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175975] [<c01c10ae>] vfs_lstat_fd+0x1e/0x50
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175982] [<c01c1228>] sys_fstatat64+0x48/0x60
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175990] [<c0103f6b>] sysenter_do_call+0x12/0x2f
Mar 27 11:05:49 XPS-1 kernel: [ 7301.175999] [<c0500000>] ? relay_hotcpu_callback+0x4d/0xbd
Mar 27 11:05:49 XPS-1 kernel: [ 7301.176034] ---[ end trace 9ff3116a5fd25f1f ]---
Mar 27 11:05:49 XPS-1 kernel: [ 7301.177450] lost page write due to I/O error on sdb1
Mar 27 11:05:49 XPS-1 kernel: [ 7301.177527] lost page write due to I/O error on sdb1

I have not gotten the stack trace every time this happens, so that may be incidental to the fundamental problem.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
MachineType: Dell Inc. XPS M1330
Package: linux-image-2.6.28-11-generic 2.6.28-11.37
ProcCmdLine: root=UUID=52bfcdb8-5615-4225-b411-3cc63da13a24 ro quiet splash crashkernel=384M-2G:64M@16M,2G-:128M@16M
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.37-generic
SourcePackage: linux

[Steve Conklin (sconklin)]

Since this is a new piece of hardware, I can't rule out a hardware failure. I'll test on other systems as well.

Also, once the error occurs, unplugging and replugging the drive USB cable isn't enough to have it be recognized again - power to the drive enclosure must be cycled.

The enclosure is sold as the "iMicro IEEE & USB Combo enclosure for 3.5" IDE HDD"

[Steve Conklin (sconklin)]

I'll bring the drive with me to the kernel sprint

[David Nielsen (davidnielsen-deactivatedaccount)]

I can confirm this with my external 750gb WD drive. It's utterly annoying since I use it to store all my files and watching a movie followed by having it halt every 5 mins when the drive is disconnected is mildly put unacceptable.

[Steve Conklin (sconklin)]

David,

could you please run "apport-collect 349767"? This will collect your system hardware information and add them to this bug.

[David Nielsen (davidnielsen-deactivatedaccount)]

Architecture: amd64
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=f76b8c99-199e-4864-a52e-394220a5893a
MachineType: LENOVO 0768FSG
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-5-generic root=UUID=65db10ef-ce74-426a-b2ee-47105e751c75 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=da_DK.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
RelatedPackageVersions: linux-backports-modules-2.6.31-5-generic N/A
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/30/07
dmi.bios.vendor: LENOVO
dmi.bios.version: 63ET62WW
dmi.board.name: CAPELL VALLEY(NAPA) CRB
dmi.board.vendor: LENOVO
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr63ET62WW:bd04/30/07:svnLENOVO:pn0768FSG:pvr3000N100:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 0768FSG
dmi.product.version: 3000 N100
dmi.sys.vendor: LENOVO

[Robbie Williamson (robbiew)]

Steve, does this still happen with Lucid Alpha 3?

[Jerone Young (jerone)]

Very old bug for 9.10 beta. Does any see this issues with 2.6.31-20 kernel, released today.

I will try this with a 1.5GB Western Digital drive I have. This issue is more then likely resolved in 9.10.

[Jerone Young (jerone)]

I am not seeing this issue in 9.10 using 2.6.31-20 kernel using Western Digital 1.5GB driver hooked up via usb, esata, & firewire.

I left it connected more then 24 hours.

This bug was orginally reported for 9.04

[Fabus (fabian-gebert-hh)]

I am suffering from this. 10.04 32-bit, Intel Mac Mini, all ports the same. Cannot reproduce, it just happens at least once per day. Got the Western Digital 1.5GB, ext4, USB 2.0, Enermax Jazz case.
How can I help solving this issue?

May 1 11:13:47 fabian kernel: [ 1974.056390] usb 1-6: USB disconnect,
address 12
May 1 11:13:47 fabian kernel: [ 1974.056995] sd 5:0:0:0: Device
offlined - not ready after error recovery
May 1 11:13:47 fabian kernel: [ 1974.057039] sd 5:0:0:0: [sdb]
Unhandled error code
May 1 11:13:47 fabian kernel: [ 1974.057045] sd 5:0:0:0: [sdb] Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
May 1 11:13:47 fabian kernel: [ 1974.057052] sd 5:0:0:0: [sdb] CDB:
Read(10): 28 00 14 21 92 7f 00 00 f0 00
May 1 11:13:47 fabian kernel: [ 1974.057073] end_request: I/O error,
dev sdb, sector 337744511
May 1 11:13:47 fabian kernel: [ 1974.057133] sd 5:0:0:0: [sdb]
Unhandled error code
May 1 11:13:47 fabian kernel: [ 1974.057137] sd 5:0:0:0: [sdb] Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
May 1 11:13:47 fabian kernel: [ 1974.057144] sd 5:0:0:0: [sdb] CDB:
Read(10): 28 00 14 21 93 6f 00 00 10 00
May 1 11:13:47 fabian kernel: [ 1974.057164] end_request: I/O error,
dev sdb, sector 337744751
May 1 11:13:48 fabian kernel: [ 1974.573204] JBD2: I/O error detected
when updating journal superblock for sdb1-8.
May 1 11:13:48 fabian kernel: [ 1974.578035] EXT4-fs (sdb1): previous
I/O error to superblock detected

Replugging doesn't help me either, I need to restart the device, even though the case LED is still on and the drive is active.

[Thorsten Hesemeyer (thorsten-hesemeyer)]

Have the same issue with Lucid on Lenovo Thinkpad W500 with external Hitachi HTS72101 0G9SA00 hard drive when copying data from the external drive to local hard drive and vice versa.

Kernel 2.6.32-22-generic-pae
Description: Ubuntu 10.04 LTS
Release: 10.04
Codename: lucid

This issue highly depends on the hardware combination.
1. other external hard drives like Lenovo secure hard disk 160GB do not show this issue
2. same Hitachi HDD attached to a Lenovo Thinkpad T61p does not have this issue.

/var/log/messages entries when copying fails:
May 11 16:33:20 user-laptop kernel: [ 5060.404169] usb 1-1: USB disconnect, address 5
May 11 16:33:20 user-laptop kernel: [ 5060.404227] sd 7:0:0:0: [sdc] Unhandled error code
May 11 16:33:20 user-laptop kernel: [ 5060.404234] sd 7:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
May 11 16:33:20 user-laptop kernel: [ 5060.404244] sd 7:0:0:0: [sdc] CDB: Read(10): 28 00 01 3c 23 df 00 00 f0 00
May 11 16:33:20 user-laptop kernel: [ 5060.404334] sd 7:0:0:0: [sdc] Unhandled error code
May 11 16:33:20 user-laptop kernel: [ 5060.404340] sd 7:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
May 11 16:33:20 user-laptop kernel: [ 5060.404348] sd 7:0:0:0: [sdc] CDB: Read(10): 28 00 01 3c 24 cf 00 00 10 00
May 11 16:33:20 user-laptop kernel: [ 5060.404394] sd 7:0:0:0: [sdc] Unhandled error code
May 11 16:33:20 user-laptop kernel: [ 5060.404399] sd 7:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
May 11 16:33:20 user-laptop kernel: [ 5060.404407] sd 7:0:0:0: [sdc] CDB: Read(10): 28 00 01 3c 24 df 00 00 f0 00
May 11 16:33:20 user-laptop kernel: [ 5060.604527] usb 3-1: new full speed USB device using uhci_hcd and address 10
May 11 16:33:21 user-laptop kernel: [ 5061.164236] usb 3-1: new full speed USB device using uhci_hcd and address 11
May 11 16:33:21 user-laptop kernel: [ 5061.724045] usb 3-1: new full speed USB device using uhci_hcd and address 12
May 11 16:33:22 user-laptop kernel: [ 5062.244102] usb 3-1: new full speed USB device using uhci_hcd and address 13

The partition /dev/sdc1 is now "unmounted" and the complete drive is unavailable.

Kind regards,
Thorsten

[Thorsten Hesemeyer (thorsten-hesemeyer)]

Additional comment:

After the device has failed:
1. device is not listed with "lsusb" any more
2. every call of "lsusb" produces four lines with increasing adress numbers like these in /var/log/messages:
May 11 17:12:22 user-laptop kernel: [ 7402.560103] usb 6-1: new full speed USB device using uhci_hcd and address 10
May 11 17:12:23 user-laptop kernel: [ 7403.176101] usb 6-1: new full speed USB device using uhci_hcd and address 11
May 11 17:12:23 user-laptop kernel: [ 7403.736083] usb 6-1: new full speed USB device using uhci_hcd and address 12
May 11 17:12:24 user-laptop kernel: [ 7404.312110] usb 6-1: new full speed USB device using uhci_hcd and address 13

Several strange CPU state udev REMOVE and ADD events happen, during the drive failure.
See appended log for details.

Kind regards,
Thorsten

[Herco van Brug (hercovanbrug)]

i have random usb harddisk disconnects too. what i'm seeing is when i copy several GB of data to it, it will stop working after a while (several minutes), show this in the /var/log/messages:

May 30 08:56:21 eeepc kernel: [28603.462424] usb 1-3: USB disconnect, address 66
May 30 08:56:28 eeepc kernel: [28610.304144] usb 1-3: new high speed USB device using ehci_hcd and address 67
May 30 08:56:28 eeepc kernel: [28610.449760] usb 1-3: configuration #1 chosen from 1 choice
May 30 08:56:28 eeepc kernel: [28610.452094] scsi49 : SCSI emulation for USB Mass Storage devices
May 30 08:56:33 eeepc kernel: [28615.452975] scsi 49:0:0:0: Direct-Access SAMSUNG HM250JI PQ: 0 ANSI: 2 CCS
May 30 08:56:33 eeepc kernel: [28615.457023] sd 49:0:0:0: Attached scsi generic sg2 type 0
May 30 08:56:33 eeepc kernel: [28615.468424] sd 49:0:0:0: [sdaf] 488397168 512-byte logical blocks: (250 GB/232 GiB)
May 30 08:56:33 eeepc kernel: [28615.470035] sd 49:0:0:0: [sdaf] Write Protect is off
May 30 08:56:33 eeepc kernel: [28615.471819] sdaf: sdaf1
May 30 08:56:33 eeepc kernel: [28616.155880] sd 49:0:0:0: [sdaf] Attached SCSI disk
May 30 09:07:47 eeepc kernel: [29289.325424] usb 1-3: USB disconnect, address 67
May 30 09:07:53 eeepc kernel: [29295.813083] usb 1-3: new high speed USB device using ehci_hcd and address 68
May 30 09:07:53 eeepc kernel: [29295.961819] usb 1-3: configuration #1 chosen from 1 choice
May 30 09:07:53 eeepc kernel: [29295.962887] scsi50 : SCSI emulation for USB Mass Storage devices
May 30 09:07:58 eeepc kernel: [29300.961156] scsi 50:0:0:0: Direct-Access SAMSUNG HM250JI PQ: 0 ANSI: 2 CCS
May 30 09:07:58 eeepc kernel: [29300.969111] sd 50:0:0:0: Attached scsi generic sg2 type 0
May 30 09:07:58 eeepc kernel: [29300.970691] sd 50:0:0:0: [sdag] 488397168 512-byte logical blocks: (250 GB/232 GiB)
May 30 09:07:58 eeepc kernel: [29300.971556] sd 50:0:0:0: [sdag] Write Protect is off
May 30 09:07:59 eeepc kernel: [29300.973984] sdag: sdag1
May 30 09:07:59 eeepc kernel: [29301.576354] sd 50:0:0:0: [sdag] Attached SCSI disk
May 30 09:08:31 eeepc kernel: [29333.974797] usb 1-3: USB disconnect, address 68
May 30 09:08:48 eeepc kernel: [29350.240135] usb 1-3: new high speed USB device using ehci_hcd and address 69
May 30 09:08:48 eeepc kernel: [29350.600147] usb 1-3: new high speed USB device using ehci_hcd and address 70
May 30 09:08:48 eeepc kernel: [29350.742977] usb 1-3: configuration #1 chosen from 1 choice
May 30 09:08:48 eeepc kernel: [29350.745284] scsi51 : SCSI emulation for USB Mass Storage devices
May 30 09:08:48 eeepc kernel: [29350.894418] usb 1-3: USB disconnect, address 70
May 30 09:08:56 eeepc kernel: [29358.756137] usb 1-3: new high speed USB device using ehci_hcd and address 71
May 30 09:08:56 eeepc kernel: [29358.905855] usb 1-3: configuration #1 chosen from 1 choice
May 30 09:08:56 eeepc kernel: [29358.908400] scsi52 : SCSI emulation for USB Mass Storage devices
May 30 09:09:01 eeepc kernel: [29363.909172] scsi 52:0:0:0: Direct-Access SAMSUNG HM250JI PQ: 0 ANSI: 2 CCS
May 30 09:09:01 eeepc kernel: [29363.920525] sd 52:0:0:0: Attached scsi generic sg2 type 0
May 30 09:09:01 eeepc kernel: ...

[Herco van Brug (hercovanbrug)]

i should perhaps also mention that this happens on 3 different linux machines that i tested on. one is fresh installed, 2 are upgraded from 9.10, all 3 have usb issues now. all had no problems with usb devices before the upgrade to 10.04.
i would opt for an increase in priority of this issue as all 3 systems are less than reliable at the moment and 2 of them 'need' to be running 24/7.

[Fabus (fabian-gebert-hh)]

see #580983

[Bogdan (bogdan-veringioiu)]

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vrnb 2294 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0580000 irq 16'
   Mixer name : 'Conexant CX20549 (Venice)'
   Components : 'HDA:14f15045,103c30d5,00100100'
   Controls : 19
   Simple ctrls : 9
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=c7b48149-823b-4ebd-b987-6c5c5bf193aa
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP 530 Notebook PC(GJ269AA#ABB)
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-22-generic root=UUID=93af652d-787a-4acc-b2f7-eb50a70c00b2 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-22.60-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-22-generic N/A
 linux-firmware 1.26
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
Uname: Linux 2.6.31-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/23/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MVU Ver. F.04
dmi.board.name: 30D5
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 82.14
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVUVer.F.04:bd05/23/2007:svnHewlett-Packard:pnHP530NotebookPC(GJ269AA#ABB):pvrF.04:rvnHewlett-Packard:rn30D5:rvrKBCVersion82.14:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP 530 Notebook PC(GJ269AA#ABB)
dmi.product.version: F.04
dmi.sys.vendor: Hewlett-Packard

[Fabus (fabian-gebert-hh)]

is there actually any progress on this issue? Any further information required to find the bug?

[Fabus (fabian-gebert-hh)]

I've just experienced this bug like 4 times in a row. How can I help? The hardware is brand new and it doesn't happen under Mac OS X (same computer).

[Fabus (fabian-gebert-hh)]

also reported here: https://bugs.launchpad.net/ubuntu/+bug/622494

[Andy Wilkinson (andy-wtribe)]

This is happening to me on ubuntu-server 10.04 x64, as well, with an xhci 1.0TB WD and two different ehci Seagates (1.0TB, 500GB). This is a serious problem as we are using these USB drives for nightly backup purposes, and this is causing the backups to fail.

Let me know what logs, etc. I can include to help out.

[Andy Wilkinson (andy-wtribe)]

As a follow-up: once this starts happening, there's almost nothing I can do to prevent it: it happens almost every time I try to do anything to the drives. Also: all of the drives work just fine in Windows on the machine in question as well as other machines.

[Budoc (budoc)]

As an additional comment, this happens on both an externally powered Freecom 500 Gb external USB drive that is identified in /var/log/messages as SAMSUNG HD501LJ which is formatted to EXT-3, and a USB-powered WD My Passport 140 GB drive that is identified as WD 1600BEA External 1.04 in /var/log/messages which is formatted to NTFS. The most recent disconnection that I have observed was when I was playing mp3s using mpd with the Freecom 500 Gb drive. The relevant portion of /var/log/messages concerning the disconnection is reproduced below. Scanning the drive with gparted reveals that there are no problems with it. Please let me know if there is anything that I can do to help identify this bug.

Sep 23 18:27:18 tosh kernel: [22266.936060] usb 1-5: new high speed USB device using ehci_hcd and address 2
Sep 23 18:27:18 tosh kernel: [22267.068965] usb 1-5: configuration #1 chosen from 1 choice
Sep 23 18:27:19 tosh kernel: [22267.872396] Initializing USB Mass Storage driver...
Sep 23 18:27:19 tosh kernel: [22267.872526] scsi4 : SCSI emulation for USB Mass Storage devices
Sep 23 18:27:19 tosh kernel: [22267.872701] usbcore: registered new interface driver usb-storage
Sep 23 18:27:19 tosh kernel: [22267.872705] USB Mass Storage support registered.
Sep 23 18:27:24 tosh kernel: [22272.873482] scsi 4:0:0:0: Direct-Access SAMSUNG HD501LJ PQ: 0 ANSI: 2 CCS
Sep 23 18:27:24 tosh kernel: [22272.875871] sd 4:0:0:0: Attached scsi generic sg2 type 0
Sep 23 18:27:24 tosh kernel: [22272.877019] sd 4:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Sep 23 18:27:24 tosh kernel: [22272.877516] sd 4:0:0:0: [sdb] Write Protect is off
Sep 23 18:27:24 tosh kernel: [22272.878897] sdb: sdb1
Sep 23 18:27:24 tosh kernel: [22272.906582] sd 4:0:0:0: [sdb] Attached SCSI disk
Sep 23 18:27:27 tosh kernel: [22275.421597] kjournald starting. Commit interval 5 seconds
Sep 23 18:27:27 tosh kernel: [22275.422649] EXT3 FS on sdb1, internal journal
Sep 23 18:27:27 tosh kernel: [22275.422659] EXT3-fs: mounted filesystem with ordered data mode.
Sep 23 18:34:25 tosh kernel: [22694.112071] usb 1-5: reset high speed USB device using ehci_hcd and address 2
Sep 23 18:34:36 tosh kernel: [22704.356066] usb 1-5: reset high speed USB device using ehci_hcd and address 2
Sep 23 18:34:36 tosh kernel: [22705.049836] usb 1-5: USB disconnect, address 2
Sep 23 18:34:36 tosh kernel: [22705.049915] sd 4:0:0:0: Device offlined - not ready after error recovery
Sep 23 18:34:36 tosh kernel: [22705.049931] sd 4:0:0:0: [sdb] Unhandled error code
Sep 23 18:34:36 tosh kernel: [22705.049937] sd 4:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
Sep 23 18:34:36 tosh kernel: [22705.049946] sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 1d 27 b8 df 00 00 f0 00
Sep 23 18:34:36 tosh kernel: [22705.050118] sd 4:0:0:0: [sdb] Unhandled error code
Sep 23 18:34:36 tosh kernel: [22705.050123] sd 4:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Sep 23 18:34:36 tosh kernel: [22705.050131] sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 1d 27 b9 cf 00 00 f0 00
Sep 23 18:34:37 tosh kernel: [22705.300104] usb 1-5: new high speed USB device using ehci_hcd and address 3
Sep 23 18...

[Budoc (budoc)]

I forgot to add that this is with Ubuntu 10.04 using Linux 2.6.32-24-generic on i686. I've only noticed this issue with 10.04.

[Cerowain (dermot-swampgum)]

I am seeing this same issue under 10.10 with kernel 2.6.35-22-generic. This is running on a standard Sun Ultra 27 Workstation.

Using a SanDisk U3 Titanium USB stick in this case, but it happens with all my USB hard drives.

Details from syslog follow.

Oct 28 11:45:31 burra kernel: [249424.002680] scsi 10:0:0:0: Direct-Access SanDisk U3 Titanium 7.01 PQ: 0 ANSI: 0 CCS
Oct 28 11:45:31 burra kernel: [249424.003316] sd 10:0:0:0: Attached scsi generic sg3 type 0
Oct 28 11:45:31 burra kernel: [249424.004151] sd 10:0:0:0: [sdc] 15745023 512-byte logical blocks: (8.06 GB/7.50 GiB)
Oct 28 11:45:31 burra kernel: [249424.004616] sd 10:0:0:0: [sdc] Write Protect is off
Oct 28 11:45:31 burra kernel: [249424.004623] sd 10:0:0:0: [sdc] Mode Sense: 45 00 00 08
Oct 28 11:45:31 burra kernel: [249424.004627] sd 10:0:0:0: [sdc] Assuming drive cache: write through
Oct 28 11:45:31 burra kernel: [249424.006533] sd 10:0:0:0: [sdc] Assuming drive cache: write through
Oct 28 11:45:31 burra kernel: [249424.006539] sdc: sdc1
Oct 28 11:45:31 burra kernel: [249424.009011] sd 10:0:0:0: [sdc] Assuming drive cache: write through
Oct 28 11:45:31 burra kernel: [249424.009016] sd 10:0:0:0: [sdc] Attached SCSI removable disk
Oct 28 11:46:13 burra kernel: [249465.229023] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:46:44 burra kernel: [249496.024807] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:47:15 burra kernel: [249526.902013] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:47:46 burra kernel: [249557.855677] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:48:17 burra kernel: [249588.731214] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:48:48 burra kernel: [249619.686586] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:48:48 burra kernel: [249619.837111] sd 10:0:0:0: [sdc] Unhandled error code
Oct 28 11:48:48 burra kernel: [249619.837115] sd 10:0:0:0: [sdc] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
Oct 28 11:48:48 burra kernel: [249619.837119] sd 10:0:0:0: [sdc] CDB: Write(10): 2a 00 00 89 bb 4e 00 00 f0 00
Oct 28 11:48:48 burra kernel: [249619.837129] end_request: I/O error, dev sdc, sector 9026382
Oct 28 11:49:20 burra kernel: [249651.599308] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:49:51 burra kernel: [249682.474875] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:50:22 burra kernel: [249713.430194] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:50:53 burra kernel: [249744.305790] usb 2-5: reset high speed USB device using ehci_hcd and address 12
Oct 28 11:51:10 burra kernel: [249761.260264] INFO: task nautilus:26666 blocked for more than 120 seconds.
Oct 28 11:51:10 burra kernel: [249761.260269] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 28 11:51:10 burra kernel: [249761.260272] nautilus D 00000001017d7962 0 26666 9859 0x00000000
Oct 28 11:51:10 burra kernel: [249761.260278] ffff88002a82b938 0000000000000082 ffff880000000000 00000000000...

[Mario Vukelic (kreuzsakra)]

I can trigger this quite reliably in Lucid. It seems to happen with 3 of my 4 external USB disks, at least so far. I just need to copy a few hundred GB of data, and most days it will happen eventually - sometimes rather quickly, sometimes it copies for a few hours before happening. So long in fact that it may be by chance that it hasn't happened with the 4th disk yet.

I tried the Natty kernel 2.6.36-1-generic from the kernel ppa, and after happily copying 200 GB it happened with that, too.

[Albert Weichselbraun (albert-weichselbraun)]

I have run into this bug as well, but could make the following observations:
 (a) this problem does not appear if you use a kernel <= 2.6.31 (that's actually my current "solution" - running lucid using the 2.6.31 kernel)
 (b) this bug strikes on my IBM/Lenovo X41(Intel 82801 FB/FBM/FR/FW/FRM (ICH6 Family) USB chipset) as well as on my company's Dell Optiplex 745 (Intel 82801H (ICH8 Family) USB chipset). My company's Lenovo X200 featuring an Intel ICH9 chipset is not affected.
 (c) its quite safe to use "older" USB disks such as a Maxtor 320GB external drive, but newer drives are highly sensitive to this bug.

Maybe there is some feature for external USB drives which got supported in 2.6.32 triggering this bug on drives supporting it.

[Mario Vukelic (kreuzsakra)]

Adding to comments #50 and #51:

My machine is a MacBook Pro 5.4. lspci gives me the following USB controller info:

00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:06.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:06.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)

I did not experience this issue on Karmic (and I did already back then perform these large copies for backup), which fits with the info in comment #51 that the 2.6.31 kernel does not exhibit the issue. It appeared for me during the Lucid development cycle, then went away again after some kernel update still before release. Since then I have unfortunately not performed copy operations with such large amounts of data (and usually it works even today when copying smaller amounts), so I cannot say for sure when it reappeared (or indeed whether the experienced initial disappearance in Lucid was a fluke and the bug just never got triggered by chance).

Different to what Albert in #51 sees, I have experienced the problem with tow oldish 300 GB disks and a 1 TB disk, but have yet to see it with my brand new 2 TB one.

I get the impression that I can trigger it more easily when using rsync via the BackInTime backup tool than when using cp or Nautilus. However, that may be by chance, and I certainly *have* triggered it with cp and Nautilus, too.

[Nick B. (futurepilot)]

If it helps I was able to catch one of these disconnects with usbmon. It looks like the disconnect happened at line 12382.

[István Kondor (kondor)]

I suffer from the same bug.
Unlike Albert Weichselbraun I also encountered this using kernel 2.6.31-20 (and 2.6.35-7).
I have 2 pieces of 2TB WD greenpower hdds in one external Raidsonic case connected via one usb port (JBOD system).
This happens despite of the fact that the disks were idling (contrary to what others mentioned so far).

This is extremely irritating since after the last line the devices disappear from /dev/sdx so I cannot even manually remount them. Restarting the PC does not help nor does disconnecting the USB cable. The only solution so far was to power down the external case.

Any suggestions would be highly appreciated!

kernel log:
kernel: [252789.528077] usb 1-3: new high speed USB device using ehci_hcd and address 4
kernel: [252789.664057] scsi3 : usb-storage 1-3:1.0
kernel: [252790.665165] scsi 3:0:0:0: Direct-Access WDC WD20 EARS-00J2GB0 PQ: 0 ANSI: 2 CCS
kernel: [252790.665903] scsi 3:0:0:1: Direct-Access WDC WD20 EARS-00S8B1 PQ: 0 ANSI: 2 CCS
kernel: [252790.666583] sd 3:0:0:0: Attached scsi generic sg2 type 0
kernel: [252790.666802] sd 3:0:0:1: Attached scsi generic sg3 type 0
kernel: [252790.705220] sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
kernel: [252790.706260] sd 3:0:0:0: [sdb] Write Protect is off
kernel: [252790.706268] sd 3:0:0:0: [sdb] Mode Sense: 00 38 00 00
kernel: [252790.706272] sd 3:0:0:0: [sdb] Assuming drive cache: write through
kernel: [252790.708569] sd 3:0:0:0: [sdb] Assuming drive cache: write through
kernel: [252790.708585] sdb:
kernel: [252790.716782] sd 3:0:0:1: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
kernel: [252790.717686] unknown partition table
kernel: [252790.722066] sd 3:0:0:1: [sdc] Write Protect is off
kernel: [252790.722076] sd 3:0:0:1: [sdc] Mode Sense: 00 38 00 00
kernel: [252790.722081] sd 3:0:0:1: [sdc] Assuming drive cache: write through
kernel: [252790.725025] sd 3:0:0:0: [sdb] Assuming drive cache: write through
kernel: [252790.725037] sd 3:0:0:0: [sdb] Attached SCSI disk
kernel: [252790.726222] sd 3:0:0:1: [sdc] Assuming drive cache: write through
kernel: [252790.726238] sdc: unknown partition table
kernel: [252790.746133] sd 3:0:0:1: [sdc] Assuming drive cache: write through
kernel: [252790.746146] sd 3:0:0:1: [sdc] Attached SCSI disk
kernel: [252792.484993] EXT4-fs (sdc): recovery complete
kernel: [252792.485636] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts: (null)
kernel: [252792.801099] EXT4-fs (sdb): recovery complete
kernel: [252792.801704] EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: (null)
kernel: [411692.542758] usb 1-3: USB disconnect, address 5
kernel: [411736.844265] JBD2: I/O error detected when updating journal superblock for sdc-8.
kernel: [411755.473553] JBD2: I/O error detected when updating journal superblock for sdb-8.

[Mario Vukelic (kreuzsakra)]

I reproduced the error with the mainline kernel build (and without any proprietary modules), as per https://wiki.ubuntu.com/Kernel/MainlineBuilds. Version tested was linux-image-2.6.35-02063504-generic_2.6.35-02063504.201008271919_amd64.deb, which is the corresponding version to Maverick's 2.6.35-22.35, as per http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html.

[Mario Vukelic (kreuzsakra)]

Like Albert Weichselbraun in comment #51, I had a much better experience with kernel 2.6.31. I could not *really* reproduce the error, and if I did, then it was a much more benign version of the bug (see further down for details). For testing I used version 2.6.31-22.67 (amd64) from the Karmic repos, along with the accompanying header files to let dkms compile the current nvidia drivers (as installed in Maverick).

Using the Karmic kernel, my backup solution (backintime) managed to backup the complete set (full backup, not incremental) of several hundred GBs from 3 external USB disks to a 4th one (and the laptop's internal disk, too, but that one never posed a problem even with the buggy kernels).

I wrote that I could not *really* reproduce it because the backup dd not run in one go without a problem: at one point in the middle of rsync'ing, all external disks did disconnect, which certainly should not happen. However, they remounted automatically and the whole episode did not lead to the nasty logfile entries about usb issues, which have been posted repeatedly above. The backup continued, and the files that were missed during the disconnect were picked up on a subsequent run.

This is remarkably different to the behavior of the other reported kernels, where the disconnect (1) leads to the nasty logfile entries, and (2) after that has happened once, the usb system seems to be in an incoherent state and produces errors all the time even with disks that have not be disconnected before.

[Jim Buddin (jimbuddin)]

Just to add a +1 to this bug - I cant give exact details as I am not at my Ubuntu box, and the external drive is no longer being picked up at all, so cant lsusb it. I will try cycling the power later.

It is used as a backup drive, is a 1TB external SATA via USB, and it dropped connection during a rsync backup (leading to filling up the /mnt/backup partition with the backup data, making it impossible to log in until some remedial work was done over SSH).

I'll post back with more useful data later.

[Jim Buddin (jimbuddin)]

Ubuntu Version: 2.6.31-16-generic

Nothing comes up with lsusb (although a power cycle has brought it back to life again now). I cant find the manufacturer of the external disk but I *think* its a Lacie 1Tb, externally powered.

Hope that helps :) probably not.

[Mario Vukelic (kreuzsakra)]

One of mine is a LaCie 1 TB too.

[Rodrigo Miranda (rodrigomiranda21)]

It happens to me in Ubuntu 10.10, with an external Lacie 2big drive

[Fabus (fabian-gebert-hh)]

For me the bug only happens with my ext4-Drive, not with the NTFS one. Can anyone confirm this?

[Mario Vukelic (kreuzsakra)]

For me it happens with ext3 and ext4 drives, but I have no others.

[Fabus (fabian-gebert-hh)]

This is getting really annoying! Is there any way we can get this fixed? Further information needed?

[John B (johnb-ca)]

Just adding my observations...

On 10.04 (2.6.32-27 x86_64) with a JFS filesystem, an external Mediasonic 4-Bay enclose (JBOD) will crap out every few days with:

[421343.711477] usb 1-4.1: device descriptor read/8, error -110
[421348.840954] usb 1-4.1: device descriptor read/8, error -110
[421348.951083] sd 10:0:0:0: Device offlined - not ready after error recovery
[421348.951095] sd 10:0:0:0: [sdg] Unhandled error code
[421348.951097] sd 10:0:0:0: [sdg] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[421348.951101] sd 10:0:0:0: [sdg] CDB: Read(16): 88 00 00 00 00 01 2a 1e b9 48 00 00 00 80 00 00
[421348.951112] end_request: I/O error, dev sdg, sector 5001623880
[421348.951132] sd 10:0:0:0: rejecting I/O to offline device

etc..

I've noticed that changing the max_sectors on the drive to 1024 makes it fail much more quickly. Unfortunately, it still fails with others I've tried (128, 256, 512), though with 128 it usually runs for a few days.

[Li Fanxi (lifanxi)]

I found on my system (O2 Joggler with Debian Squeeze) that if I disable my wireless card (USB rt2870) by ifdown the interface and remove the kernel module, this problem can be reproduced within several hours. If I enable the wireless card, the problem can no longer be reproduced for weeks.

[Mike Rogers (mikerogerz)]

[111691.725819] usb 2-1: USB disconnect, address 52
[111691.725959] sd 5:0:0:0: [sdb] Unhandled error code
[111691.725961] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[111691.725965] sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 18 18 d2 a7 00 00 f0 00
[111691.726140] sd 5:0:0:0: [sdb] Unhandled error code
[111691.726142] sd 5:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[111691.726145] sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 18 18 d3 97 00 00 10 00
[111691.726165] sd 5:0:0:0: [sdb] Unhandled error code
[111691.726167] sd 5:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[111691.726170] sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 18 18 d3 a7 00 00 f0 00

[Matej Kenda (matejken)]

Bug 701011 is similar to this one. Complete USB traces are available there.

[abadger (dave-netfm)]

I see this problem on a HP DL380 server .. the usb drive is currently unavailable:-

root@ubuntu:/var/log# uname -a
Linux ubuntu 2.6.32-27-server #49-Ubuntu SMP Thu Dec 2 02:05:21 UTC 2010 x86_64 GNU/Linux

Jan 23 08:21:55 ubuntu kernel: [648744.030323] usb 1-8.1: reset high speed USB device using ehci_hcd and address 5
Jan 23 08:21:55 ubuntu kernel: [648744.270318] usb 1-8.1: reset high speed USB device using ehci_hcd and address 5
Jan 23 08:21:59 ubuntu kernel: [648748.357759] sd 3:0:0:1: [sdb] Unhandled error code
Jan 23 08:21:59 ubuntu kernel: [648748.357765] sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jan 23 08:21:59 ubuntu kernel: [648748.357769] sd 3:0:0:1: [sdb] CDB: Read(10): 28 20 3c 34 73 5f 00 00 f0 00
Jan 23 08:22:30 ubuntu kernel: [648779.000233] usb 1-8.1: reset high speed USB device using ehci_hcd and address 5
Jan 23 08:22:35 ubuntu kernel: [648784.192808] usb 1-8.1: reset high speed USB device using ehci_hcd and address 5
Jan 23 08:22:50 ubuntu kernel: [648798.840292] usb 1-8.1: reset high speed USB device using ehci_hcd and address 5
Jan 23 08:22:50 ubuntu kernel: [648799.070288] usb 1-8.1: reset high speed USB device using ehci_hcd and address 5
Jan 23 08:22:54 ubuntu kernel: [648803.148230] sd 3:0:0:1: [sdb] Unhandled error code
Jan 23 08:22:54 ubuntu kernel: [648803.148236] sd 3:0:0:1: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jan 23 08:22:54 ubuntu kernel: [648803.148240] sd 3:0:0:1: [sdb] CDB: Read(10): 28 20 6b 07 63 8f 00 00 30 00
Jan 23 08:23:25 ubuntu kernel: [648833.940333] usb 1-8.1: reset high speed USB device using ehci_hcd and address 5
Jan 23 08:46:52 ubuntu kernel: [650240.700241] usb 1-8.1: reset high speed USB device using ehci_hcd and address 5
Jan 23 08:46:52 ubuntu kernel: [650240.930237] usb 1-8.1: reset high speed USB device using ehci_hcd and address 5
Jan 23 08:46:56 ubuntu kernel: [650245.022309] sd 3:0:0:1: [sdb] Unhandled error code

root@ubuntu:/var/log# lsusb
Bus 006 Device 003: ID 03f0:1327 Hewlett-Packard
Bus 006 Device 002: ID 03f0:1027 Hewlett-Packard
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 4971:1002 SimpleTech
Bus 001 Device 003: ID 4971:1005 SimpleTech
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@ubuntu:/var/log#

root@ubuntu:/var/log# fdisk -l

Disk /dev/cciss/c0d0: 733.9 GB, 733910294528 bytes
255 heads, 63 sectors/track, 89226 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e9148

           Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 85613 687679488 83 Linux
/dev/cciss/c0d0p2 85613 89227 29027329 5 Extended
/dev/cciss/c0d0p5 85613 89227 29027328 82 Linux swap / Solaris

Disk /dev/sda: 4072 MB...

[Matej Kenda (matejken)]

On the machine where USB disc gets disconnected generally after two days
uptime, we have disabled the USB power management and this problem didn't
happen for cca 6 days uptime.

Following script has been added to the file /etc/rc.local

for i in /sys/bus/usb/devices/*/power/level; do echo on > $i; done

On following machines:
  10.0.3.57
  10.0.3.58
  10.0.3.40
  10.0.3.39

All these machines will be monitored, if usb disconnect problem occurs

This is the command for checking usb power management setting:
for i in /sys/bus/usb/devices/*/power/level; do echo $i; cat $i; done

auto - means that power management is enabled
on - means that usb will be always on (enabled)

We don't know why this helps.

Is there a kernel boot options to enable power level for all USB devices?

See also bug 701011.

[einar.kristian (einar-kristian)]

I‘ve been experiencing the same problem for a long time for USB sticks and USB drives. LaCie 750GB, SanDisk drives. I’ll try the proposal from Matej. It‘s annoying. The LaCie sometimes when I try to copy large amount of data, disconnects and I hear the harddisk search continuously for tracks. I need to restart the LaCie. Hope the solution proposed by Matej also fixes this problem. I’m running Ubuntu on a MacMini.

[Mario Vukelic (kreuzsakra)]

Thanks Matej, unfortunately it does nothing for me. Attached are the logs after a reboot, setting the power level, and running Back in Time (i.e., rsync). The usb devices are the same as posted previously.

[Budoc (budoc)]

My drive disconnected earlier as I was playing music off of it with mpd, and would not come back online until I rebooted my computer. Turning the drive off and on again, and plugging it back into the usb port failed to get it working. Only after a reboot did it work again. I noticed a few things in my /var/log/messages that I hadn't seen before. Usually, I just get the first four lines of what I've reproduced below. I'm not sure if what is below is related to mpd or related to the drive, so apologies in advance if this post isn't helpful to the discussion. The details for this drive are given in post #47.

Feb 4 00:10:34 tosh kernel: [29023.505128] usb 1-3: USB disconnect, address 2
Feb 4 00:10:39 tosh kernel: [29028.016064] scsi 4:0:0:0: [sdb] Unhandled error code
Feb 4 00:10:39 tosh kernel: [29028.016073] scsi 4:0:0:0: [sdb] Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
Feb 4 00:10:39 tosh kernel: [29028.016083] scsi 4:0:0:0: [sdb] CDB: Read(10): 28 00 08 2c 10 4f 00 00 20 00
Feb 4 00:10:39 tosh kernel: [29028.017279] ------------[ cut here ]------------
Feb 4 00:10:39 tosh kernel: [29028.017294] WARNING: at /build/buildd/linux-2.6.35/fs/buffer.c:1151 mark_buffer_dirty+0x70/0x90()
Feb 4 00:10:39 tosh kernel: [29028.017301] Hardware name: 00000000000000000000
Feb 4 00:10:39 tosh kernel: [29028.017305] Modules linked in: usb_storage aes_i586 aes_generic lib80211_crypt_ccmp binfmt_misc parport_pc ppdev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_seq_midi pcmcia joydev snd_rawmidi i915 drm_kms_helper snd_seq_midi_event snd_seq drm psmouse intel_agp snd_timer snd_seq_device snd agpgart yenta_socket pcmcia_rsrc ipw2200 i2c_algo_bit soundcore snd_page_alloc serio_raw video pcmcia_core output tifm_7xx1 tifm_core libipw cfg80211 lib80211 lp parport 8139too firewire_ohci sdhci_pci 8139cp firewire_core sdhci led_class crc_itu_t mii
Feb 4 00:10:39 tosh kernel: [29028.017405] Pid: 19814, comm: mpd Not tainted 2.6.35-25-generic #44-Ubuntu
Feb 4 00:10:39 tosh kernel: [29028.017411] Call Trace:
Feb 4 00:10:39 tosh kernel: [29028.017425] [<c014ad42>] warn_slowpath_common+0x72/0xa0
Feb 4 00:10:39 tosh kernel: [29028.017434] [<c023d7f0>] ? mark_buffer_dirty+0x70/0x90
Feb 4 00:10:39 tosh kernel: [29028.017442] [<c023d7f0>] ? mark_buffer_dirty+0x70/0x90
Feb 4 00:10:39 tosh kernel: [29028.017452] [<c014ad92>] warn_slowpath_null+0x22/0x30
Feb 4 00:10:39 tosh kernel: [29028.017460] [<c023d7f0>] mark_buffer_dirty+0x70/0x90
Feb 4 00:10:39 tosh kernel: [29028.017470] [<c0281f9a>] T.1020+0x4a/0x70
Feb 4 00:10:39 tosh kernel: [29028.017479] [<c028202b>] ext3_handle_error+0x6b/0xc0
Feb 4 00:10:39 tosh kernel: [29028.017487] [<c0281009>] ? ext3_msg+0x49/0x50
Feb 4 00:10:39 tosh kernel: [29028.017496] [<c02820d4>] __ext3_std_error+0x54/0x90
Feb 4 00:10:39 tosh kernel: [29028.017505] [<c0279732>] ext3_reserve_inode_write+0x42/0x90
Feb 4 00:10:39 tosh kernel: [29028.017514] [<c02797ab>] ext3_mark_inode_dirty+0x2b/0x50
Feb 4 00:10:39 tosh kernel: [29028.017523] [<c02798fe>] ext3_dirty_inode+0x4e/0x80
Feb 4 00:10:39 tosh kernel: [29028.017533] [<c0237561>] __mark_inode_dirty+0x31/0x190
Feb 4 00:10:39 tosh kernel: [29028.017542] ...

[NeilGreenwood (neil-greenwood)]

I found yesterday that I could log out then unplug/plug the drive
after it disconnected. Bit quicker than rebooting.

Sent from my iPod

On 4 Feb 2011, at 00:33, Budoc <email address hidden> wrote:

> My drive disconnected earlier as I was playing music off of it with
> mpd,
> and would not come back online until I rebooted my computer. Turning
> the
> drive off and on again, and plugging it back into the usb port
> failed to
> get it working. Only after a reboot did it work again. I noticed a few
> things in my /var/log/messages that I hadn't seen before. Usually, I
> just get the first four lines of what I've reproduced below. I'm not
> sure if what is below is related to mpd or related to the drive, so
> apologies in advance if this post isn't helpful to the discussion. The
> details for this drive are given in post #47.
>
> Feb 4 00:10:34 tosh kernel: [29023.505128] usb 1-3: USB disconnect,
> address 2
> Feb 4 00:10:39 tosh kernel: [29028.016064] scsi 4:0:0:0: [sdb]
> Unhandled error code
> Feb 4 00:10:39 tosh kernel: [29028.016073] scsi 4:0:0:0: [sdb]
> Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
> Feb 4 00:10:39 tosh kernel: [29028.016083] scsi 4:0:0:0: [sdb] CDB:
> Read(10): 28 00 08 2c 10 4f 00 00 20 00
> Feb 4 00:10:39 tosh kernel: [29028.017279] ------------[ cut
> here ]------------
> Feb 4 00:10:39 tosh kernel: [29028.017294] WARNING: at /build/
> buildd/linux-2.6.35/fs/buffer.c:1151 mark_buffer_dirty+0x70/0x90()
> Feb 4 00:10:39 tosh kernel: [29028.017301] Hardware name:
> 00000000000000000000
> Feb 4 00:10:39 tosh kernel: [29028.017305] Modules linked in:
> usb_storage aes_i586 aes_generic lib80211_crypt_ccmp binfmt_misc
> parport_pc ppdev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm
> snd_seq_midi pcmcia joydev snd_rawmidi i915 drm_kms_helper
> snd_seq_midi_event snd_seq drm psmouse intel_agp snd_timer
> snd_seq_device snd agpgart yenta_socket pcmcia_rsrc ipw2200
> i2c_algo_bit soundcore snd_page_alloc serio_raw video pcmcia_core
> output tifm_7xx1 tifm_core libipw cfg80211 lib80211 lp parport
> 8139too firewire_ohci sdhci_pci 8139cp firewire_core sdhci led_class
> crc_itu_t mii
> Feb 4 00:10:39 tosh kernel: [29028.017405] Pid: 19814, comm: mpd
> Not tainted 2.6.35-25-generic #44-Ubuntu
> Feb 4 00:10:39 tosh kernel: [29028.017411] Call Trace:
> Feb 4 00:10:39 tosh kernel: [29028.017425] [<c014ad42>]
> warn_slowpath_common+0x72/0xa0
> Feb 4 00:10:39 tosh kernel: [29028.017434] [<c023d7f0>] ?
> mark_buffer_dirty+0x70/0x90
> Feb 4 00:10:39 tosh kernel: [29028.017442] [<c023d7f0>] ?
> mark_buffer_dirty+0x70/0x90
> Feb 4 00:10:39 tosh kernel: [29028.017452] [<c014ad92>]
> warn_slowpath_null+0x22/0x30
> Feb 4 00:10:39 tosh kernel: [29028.017460] [<c023d7f0>]
> mark_buffer_dirty+0x70/0x90
> Feb 4 00:10:39 tosh kernel: [29028.017470] [<c0281f9a>] T.
> 1020+0x4a/0x70
> Feb 4 00:10:39 tosh kernel: [29028.017479] [<c028202b>]
> ext3_handle_error+0x6b/0xc0
> Feb 4 00:10:39 tosh kernel: [29028.017487] [<c0281009>] ? ext3_msg
> +0x49/0x50
> Feb 4 00:10:39 tosh kernel: [29028.017496] [<c02820d4>]
> __ext3_std_error+0x54/0x90
> Feb 4 00:10:39 tosh...

[John B (johnb-ca)]

Look like Matej's workaround may help for my issue at least. I set power/level to on for the USB hard drives and I've been up for 8 days and counting without an error.

Thanks!

[John B (johnb-ca)]

Spoke too soon. For some reason, it stayed up for long (8 days) than normal, but same error occurred. Also happened again 2 days later...

[Mario Vukelic (kreuzsakra)]

Upgraded to Natty. With kernel linux-image-2.6.38-2-generic at 2.6.38-3.30, I now get a kernel crash when running the backup, the content of which apparently largely is the same as previously in the error logs. Please excuse the crappy quality of the phone cam photo of the attachment.

[Mario Vukelic (kreuzsakra)]

Well actually .. while the kernel message also refers to an unhandled error code, which to my non-expert eyes looks similar to others in the logs, I see now that the kernel message starts with an ext4 IO error. So either a different issue with similar results, or possibly valuable new information?

[usbdevice (rook-e)]

I was having experiencing the same symptoms on my machine, first on Lucid and later on Maverick. Random disconnects of an external 2TB USB HDD in intervals ranging between mere minutes up to 2 hours. Even weirder, when I manually unmounted the (single) partition but left the drive running and connected, the partition would remount after a couple of minutes.

Disconnects would happen randomly, even when not accessing the drive.

I upgraded to Maverick to see if that would resolve it, no luck. I tried the power level trick, no luck.

I tried the drive on other machines (and OSses) and not once experienced these symptoms.
I do have one other external USB HDD in a 2.5" enclosure (bus powered) which does not exhibit this problem on the same machine.

On a hunch I removed the only PCI-card I have in this machine - an Adaptec SCSI controller which I only use for an old film scanner.

I have not experienced anymore disconnects since.

Driver issue? IRQ issue? I'm not knowledgeable enough to comment.

If I can help by providing logs etc. please let me know. The card is not installed anymore at the moment but can put it back in in order to provide useful information.

Lenny

[Jools Wills (jools)]

I was having disconnects after kernel 2.6.26 with a usb harddrive on an intel mac mini. No USB quirks, or max sector changes helped. in the end I traced the issue to kernel commit b963801164618e25fbdc0cd452ce49c3628b46c8

I reverted the commit (had to be done manually), and everything is rock solid for me on kernel 2.6.32 - 2.6.38

Attached is the patch I am using currently. applies to 2.6.37/2.6.38 (and maybe earlier)

[Mario Vukelic (kreuzsakra)]

Many thanks to Jools, you are a hero.

On my machine a cable change seems to have cured it. I drew a diagram of my setup below. This worked 2 or 3 years without a problem until the fatal kernel upgrade. The devices and cables are rarely being touched or moved, which is why I unfortunately neglected to check for cabling issues right away.

Laptop USB ------<5m cable>----- Cheapo active USB extension -----<1m cable>----- USB Hub -----<4x1m cable>----- 4 USB disks

Laptop USB ----- Logitech wireless mouse

The 1m cable between USB extension and hub had the damage-prone Mini-B plug (5-pin), and so it was the first I replaced on a hunch. Since then I have performed copy tests and the error did not yet reappear after > 200 GB, an amount of data that would usually have triggered it. Have the other subscribers to this bug checked their cables?

[Andrew B (andrew-berridge)]

Reading through this thread, I experienced exactly the same issue. I changed the USB cable and all is now well. Is this REALLY a bug? Like the previous poster, I would suggest that all subscribers to this bug check their cables. In the light of this, is it possible to suggest in var/log/messages that the user might like to check their cable? Difficult, I know ;-)

[Matej Kenda (matejken)]

Alan Stern posted a patch that could potentially solve the problem to linux usb mailing list.

http://thread.gmane.org/gmane.linux.usb.general/45577/focus=45587

I modified that patch to be able to apply it to Ubuntu Natty linux kernel 2.6.38. Patched kernel was then compiled on Lucid.

I started to run tests with 2.6.38 kernel on Lucid today.

[Matej Kenda (matejken)]

Good news:

Patched Linux kernel from Natty (2.6.38) is being used on several computers (COMe) for almost two weeks. USB occasionally disconnected using stock kernel.

USB disk where the complete OS is installed did not unexpectedly disconnect on any of these embedded devices.

[Seth Forshee (sforshee)]

@Matej, thanks for working with the upstream developers to make some progress on this issue!

We typically wait for a fix to be merged into Linus's tree at a minimum before pulling it into one of our releases. At this point I don't even see the patch merged into the USB development tree. Once a fix lands upstream we can take a look at pulling it into our kernels.

[Matej Kenda (matejken)]

Seth, I understand that.

I reported the results to Alan Stern and Linux USB mailing list as well. I hope that the patch will end up in the Linus' tree.

[jochenb (jochen-2)]

Hi !
Is there any news on this ?
I've got the same issue with a Lacie 1TB USB drive.
Dmesg shows a disconnect after 1 second.
The drive does not appear in lsusb or as in /dev/disk.
I' using Ubuntu 10.04.2 LTS on 2.6.32-32-generic.

Cheers,

Jochen

[51279.456013] usb 1-1: new high speed USB device using ehci_hcd and address 3
[51279.597483] usb 1-1: configuration #1 chosen from 1 choice
[51279.601119] scsi5 : SCSI emulation for USB Mass Storage devices
[51279.602039] usb-storage: device found at 3
[51279.602042] usb-storage: waiting for device to settle before scanning
[51284.600125] usb-storage: device scan complete
[51284.600620] scsi 5:0:0:0: Direct-Access SAMSUNG HD103SI PQ: 0 ANSI: 2 CCS
[51284.602141] sd 5:0:0:0: Attached scsi generic sg2 type 0
[51284.602846] sd 5:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[51284.603596] sd 5:0:0:0: [sdc] Write Protect is off
[51284.603600] sd 5:0:0:0: [sdc] Mode Sense: 34 00 00 00
[51284.603603] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[51284.605592] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[51284.605828] sdc: sdc1
[51284.618594] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[51284.618886] sd 5:0:0:0: [sdc] Attached SCSI disk
[51292.781352] usb 1-1: USB disconnect, address 3

[Matej Kenda (matejken)]

I am in contact with Alan Stern. He provided me a patch for newer Linux kernel (I am using 2.6.38).

The patch looks promising. Disconnect didn't happen with patched kernel during the 1 month test period.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Mario Vukelic (kreuzsakra)]

Dear subscribers, before going ballistic please note that the automated script closed it only for one project. It appears to still have "confirmed" status for "Linux", and "new" for "Lucid"

[Matej Kenda (matejken)]

The patch which solves the problem is available in the Linus' git:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=004c19682884d4f40000ce1ded53f4a1d0b18206

[Matej Kenda (matejken)]

Fix was released in Linux kernel 3.0.1.

http://git.kernel.org/?p=linux/kernel/git/stable/linux-3.0.y.git;a=commit;h=22007e1ddbe599373b116ecf3485ebf842405f73

and resolves upstream bug 32432

[Matej Kenda (matejken)]

Although not yet closed, upstream bug is resolved.

Can the patch be merged back to 2.6.38 kernel, which was backported to Lucid from Natty?

[Gustavo (paolo-nino)]

I tested also Oneiric beta1 live CD and I found the same problem.
If I connect a USB flash drive and I try to copy to desktop a big file like an iso image, after a few seconds the USB drive disconnect.
My computer is based on a AMD Phenom(tm) II X6 1090T Processor processors (6 cpu cores)
Logitech USB-PS/2 Optical Mouse
Logitech, G15 Keyboard
Logitech, Inc. G15 Keyboard / USB Hub
Asus Crosshair V Formula, BIOS 0506 06/22/2011

It's my first time I comment a bug.
Please let me know if I can supply more useful informations.

[Matej Kenda (matejken)]

The change that supposedly fixes this issue was added to Linux kernel 3.0.1 and should be in the Linux kernel used in Oneiric as well.

Can you provide kernel log from the time of the disconnect?

[Gustavo (paolo-nino)]

Yes I will be happy to give the kernel log but I'm not familiar with command
line.
Can you please give me the command I need to use to get the kernel log about
USB problem I mention.

2011/9/5 Matej Kenda <email address hidden>

> The change that supposedly fixes this issue was added to Linux kernel
> 3.0.1 and should be in the Linux kernel used in Oneiric as well.
>
> Can you provide kernel log from the time of the disconnect?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/349767
>
> Title:
> external USB hard drive disconnects
>
> Status in The Linux Kernel:
> Confirmed
> Status in “linux” package in Ubuntu:
> Won't Fix
> Status in “linux” source package in Lucid:
> Confirmed
>
> Bug description:
> This is a new external drive enclosure.
>
> I can easily reproduce this:
>
> Plug in the usb cable and power up the drive. System log shows:
>
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.584108] usb 2-2: new high speed USB
> device using ehci_hcd and address 7
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.720027] usb 2-2: configuration #1
> chosen from 1 choice
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.757608] Initializing USB Mass Storage
> driver...
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.762530] scsi5 : SCSI emulation for
> USB Mass Storage devices
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.768158] usbcore: registered new
> interface driver usb-storage
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.768167] USB Mass Storage support
> registered.
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.769258] scsi 5:0:0:0: Direct-Access
> WDC WD16 00JB-75GVA0 08.0 PQ: 0 ANSI: 0
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.773347] sd 5:0:0:0: [sdb] 312499999
> 512-byte hardware sectors: (159 GB/149 GiB)
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.793936] sd 5:0:0:0: [sdb] Write
> Protect is off
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.801920] sd 5:0:0:0: [sdb] 312499999
> 512-byte hardware sectors: (159 GB/149 GiB)
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.804738] sd 5:0:0:0: [sdb] Write
> Protect is off
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.804760] sdb: sdb1
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.837230] sd 5:0:0:0: [sdb] Attached
> SCSI disk
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.837377] sd 5:0:0:0: Attached scsi
> generic sg2 type 0
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.513967] kjournald starting. Commit
> interval 5 seconds
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.513995] EXT3-fs warning: maximal
> mount count reached, running e2fsck is recommended
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.515031] EXT3 FS on sdb1, internal
> journal
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.515040] EXT3-fs: recovery complete.
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.522316] EXT3-fs: mounted filesystem
> with ordered data mode.
>
> Now if I do anything that causes reads from the drive (in this case
> "du -sh /media/disk", I get the following in the log:
>
> Mar 27 11:05:48 XPS-1 kernel: [ 7300.911188] usb 2-2: reset high speed USB
> device using ehci_hcd and address 7
> Mar 27 11:05:49 XPS-1 kernel: [ 7301.173948] sd 5:0:0:0: [sdb] Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
> Mar 27 11:05:49 XP...

[Gustavo (paolo-nino)]

Ok I try to give some of my log.
When I connect my flash drive lsusb report:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 012 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 013 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 012 Device 002: ID 046d:c043 Logitech, Inc. MX320/MX400 Laser Mouse
Bus 012 Device 003: ID 046d:c223 Logitech, Inc. G11/G15 Keyboard / USB Hub
Bus 012 Device 004: ID 046d:c221 Logitech, Inc. G11/G15 Keyboard / Keyboard
Bus 012 Device 005: ID 046d:c225 Logitech, Inc. G11/G15 Keyboard / G keys
Bus 010 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade

If I start to copy a large file from USB flash drive to the desktop on
Oneiric, after just a few seconds, I get an error message and my kernel log
file say:

Sep 6 13:40:12 ninobox kernel: [ 266.120038] usb 10-2: new high speed USB
device number 2 using xhci_hcd
Sep 6 13:40:12 ninobox kernel: [ 266.140290] xhci_hcd 0000:05:00.0: WARN:
short transfer on control ep
Sep 6 13:40:12 ninobox kernel: [ 266.140368] xhci_hcd 0000:05:00.0: WARN:
short transfer on control ep
Sep 6 13:40:12 ninobox kernel: [ 266.140448] xhci_hcd 0000:05:00.0: WARN:
short transfer on control ep
Sep 6 13:40:12 ninobox kernel: [ 266.140534] xhci_hcd 0000:05:00.0: WARN:
short transfer on control ep
Sep 6 13:40:13 ninobox kernel: [ 266.785415] usbcore: registered new
interface driver uas
Sep 6 13:40:13 ninobox kernel: [ 266.786057] Initializing USB Mass Storage
driver...
Sep 6 13:40:13 ninobox kernel: [ 266.786214] scsi8 : usb-storage 10-2:1.0
Sep 6 13:40:13 ninobox kernel: [ 266.786297] usbcore: registered new
interface driver usb-storage
Sep 6 13:40:13 ninobox kernel: [ 266.786298] USB Mass Storage support
registered.
Sep 6 13:40:14 ninobox kernel: [ 267.780629] scsi 8:0:0:0:
Direct-Access SanDisk Cruzer Blade 1.03 PQ: 0 ANSI: 2
Sep 6 13:40:14 ninobox kernel: [ 268.650211] sd 8:0:0:0: Attached scsi
generic sg5 type 0
Sep 6 13:40:14 ninobox kernel: [ 268.650903] sd 8:0:0:0: [sde] 15633408
512-byte logical blocks: (8.00 GB/7.45 GiB)
Sep 6 13:40:14 ninobox kernel: [ 268.651828] xhci_hcd 0000:05:00.0: WARN:
Stalled endpoint
Sep 6 13:40:14 ninobox kernel: [ 268.652084] sd 8:0:0:0: [sde] Write
Protect is off
Sep 6 13:40:14 ninobox kernel: [ 268.652086] sd 8:0:0:0: [sde] Mode Sense:
03 00 00 00
Sep 6 13:40:14 ninobox kernel: [ 268.652199] xhci_hcd 0000:05:00.0: WARN:
Stalled endpoint
Sep 6 13:40:14 ninobox kernel: [ 268.652453] sd 8:0:0:0: [sde] No Caching
mode page present
Sep 6 13:40:14 ninobox kernel: [...

[Gustavo (paolo-nino)]

I installed oneiric and the USB bug for my computer is present.
If I connect Sundisk pen drive and do dmesg | tail command show this:
sudo dmesg | tail
[10434.820037] usb 7-2: device descriptor read/64, error -32
[10435.080034] usb 7-2: device descriptor read/64, error -32
[10435.360040] usb 7-2: new full speed USB device number 3 using ohci_hcd
[10435.510035] usb 7-2: device descriptor read/64, error -32
[10435.770034] usb 7-2: device descriptor read/64, error -32
[10436.050036] usb 7-2: new full speed USB device number 4 using ohci_hcd
[10436.470032] usb 7-2: device not accepting address 4, error -32
[10436.640034] usb 7-2: new full speed USB device number 5 using ohci_hcd
[10437.060042] usb 7-2: device not accepting address 5, error -32
[10437.060074] hub 7-0:1.0: unable to enumerate USB device on port 2

Any idea about why the new kernell 3.0.1 don't work for my
Asus Crosshair V Formula?
Please help me!

[Gustavo (paolo-nino)]

Sorry my kernel it's 3.0.0.10.11.
Is this patched with USB fix?

[Gustavo (paolo-nino)]

Now I installed kernel 3.1.0-0301rc4-generic on Oneiric but also this version don't fix my problem with USB.
I found again same error
 sudo dmesg | tail
[sudo] password for paolo:
[ 49.430060] usb 7-2: device descriptor read/64, error -32
[ 49.690061] usb 7-2: device descriptor read/64, error -32
[ 49.950063] usb 7-2: new full speed USB device number 3 using ohci_hcd
[ 50.100062] usb 7-2: device descriptor read/64, error -32
[ 50.360064] usb 7-2: device descriptor read/64, error -32
[ 50.620062] usb 7-2: new full speed USB device number 4 using ohci_hcd
[ 51.040046] usb 7-2: device not accepting address 4, error -32
[ 51.210061] usb 7-2: new full speed USB device number 5 using ohci_hcd
[ 51.630080] usb 7-2: device not accepting address 5, error -32
[ 51.630111] hub 7-0:1.0: unable to enumerate USB device on port 2

If I use different flash drive I receive always the same error
Witch is the fixed kernel version?

[Matej Kenda (matejken)]

I did a search for the error that you get: "device not accepting address 4, error -32".

It seems that it is related to using ehci USB and not to the problem discussed in this bug:

For example, see this page:

http://ubuntuforums.org/showthread.php?t=898939

[Gustavo (paolo-nino)]

Thank you for link but I already found it and directions give there don't
apply to my system.
That forum discussion suggest to disable ehci_hcd but I don't have that
modules loaded on my system.
I have xhci_hcd loaded on my system but if I do:
 sudo rmmod xhci_hcd
my USB mouse and keyboard stop working.
The only USB connection that work are USB 3.0 where I connect mouse and
keyboard.
All others USB give errors if I connect something.
My opinion is that the xhci_hcd module can manage only USB 3.0 hardware.
This is my module list:
Module Size Used by
rfcomm 48294 0
bluetooth 179403 3 rfcomm
parport_pc 37530 0
ppdev 17141 0
binfmt_misc 17646 1
dm_crypt 23761 0
usbhid 48081 0
hid 100109 1 usbhid
snd_hda_codec_hdmi 33315 4
snd_hda_codec_realtek 321980 1
snd_hda_intel 34236 3
snd_seq_midi 13370 0
snd_rawmidi 30426 1 snd_seq_midi
snd_hda_codec 108530 3
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_seq_midi_event 14899 1 snd_seq_midi
snd_hwdep 13782 1 snd_hda_codec
snd_seq 62088 2 snd_seq_midi,snd_seq_midi_event
snd_pcm 98267 3
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_seq_device 14528 3 snd_seq_midi,snd_rawmidi,snd_seq
snd_timer 30240 2 snd_seq,snd_pcm
snd 68651 16
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_rawmidi,snd_hda_codec,snd_hwdep,snd_seq,snd_pcm,snd_seq_device,snd_timer
soundcore 12680 1 snd
sp5100_tco 13787 0
lp 17868 0
snd_page_alloc 18572 2 snd_hda_intel,snd_pcm
eeepc_wmi 12911 0
psmouse 70214 0
edac_core 54597 0
asus_wmi 25013 1 eeepc_wmi
sparse_keymap 13995 1 asus_wmi
k10temp 13159 0
i2c_piix4 13287 0
edac_mce_amd 23747 0
serio_raw 13294 0
parport 42788 3 parport_pc,ppdev,lp
dm_mirror 22684 1
dm_region_hash 21033 1 dm_mirror
dm_log 18788 3 dm_mirror,dm_region_hash
e1000e 162398 0
pata_atiixp 13157 0
nouveau 757797 2
xhci_hcd 88842 0
ttm 77625 1 nouveau
ahci 26150 4
drm_kms_helper 43171 1 nouveau
libahci 31646 1 ahci
drm 238528 4 nouveau,ttm,drm_kms_helper
i2c_algo_bit 13436 1 nouveau
mxm_wmi 12979 1 nouveau
video 20027 1 nouveau
wmi 19269 2 asus_wmi,mxm_wmi

Maybe I need some other module laded to make all my USB connection to work?

2011/9/8 Matej Kenda <email address hidden>

> I did a search for the error that you get: "device not accepting address
> 4, error -32".
>
> It seems that it is related to using ehci USB and not to the problem
> discussed in this bug:
>
> For example, see this page:
>
> http://ubuntuforums.org/showthread.php?t=898939
>
> --
> You received this bug notifi...

[DiegoRivera (diego-rivera)]

Hi, all!

Any news on whether this will be backported to 2.6.38 for Natty? At this point I'm reluctant to upgrade to Oneiric (b/c I don't like to be forced into using Unity, which I've not quite warmed up to yet), but I'd still like to enjoy this fix.

Please advise.

Thanks.

[Václav Šmilauer (eudoxos)]

I am sorry to say that I am hitting this bug with 3.2.0-24-generic (stock precise kernel)., with a Samsung 500GB USB 2.0 2.5" external drive (other external hdds work just fine). Can I provide any more information?

[Wayde Nie (niew)]

I am seeing this on 12.04 LTS , 3.2.0-24-generic with all fixes/updates applied as of this morning with an iomega 2TB 'eGo' external USB drive.

[avinash (avinashreddyk)]

I am facing the same issue on 3.2.0-32-generic-pae #51-Ubuntu 12.04 LTS, for my iomega320GB external usb drive.
Please let me know if their is a fi x avaialable or should i tweak something.thnaks in advance.

[Gustavo (paolo-nino)]

Now everything works fine with Ubuntu 12.04 and my computer.
I fix the problem updating the motherboard bios.
So the problem was an hardware problem and not an Ubuntu problem for me.
I have a motherboard with USB 3.

2012/10/21 avinash <email address hidden>

> I am facing the same issue on 3.2.0-32-generic-pae #51-Ubuntu 12.04 LTS,
> for my iomega320GB external usb drive.
> Please let me know if their is a fi x avaialable or should i tweak
> something.thnaks in advance.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/349767
>
> Title:
> external USB hard drive disconnects
>
> Status in The Linux Kernel:
> Fix Released
> Status in “linux” package in Ubuntu:
> Won't Fix
> Status in “linux” source package in Lucid:
> Confirmed
>
> Bug description:
> This is a new external drive enclosure.
>
> I can easily reproduce this:
>
> Plug in the usb cable and power up the drive. System log shows:
>
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.584108] usb 2-2: new high speed USB
> device using ehci_hcd and address 7
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.720027] usb 2-2: configuration #1
> chosen from 1 choice
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.757608] Initializing USB Mass
> Storage driver...
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.762530] scsi5 : SCSI emulation for
> USB Mass Storage devices
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.768158] usbcore: registered new
> interface driver usb-storage
> Mar 27 11:05:07 XPS-1 kernel: [ 7259.768167] USB Mass Storage support
> registered.
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.769258] scsi 5:0:0:0: Direct-Access
> WDC WD16 00JB-75GVA0 08.0 PQ: 0 ANSI: 0
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.773347] sd 5:0:0:0: [sdb] 312499999
> 512-byte hardware sectors: (159 GB/149 GiB)
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.793936] sd 5:0:0:0: [sdb] Write
> Protect is off
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.801920] sd 5:0:0:0: [sdb] 312499999
> 512-byte hardware sectors: (159 GB/149 GiB)
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.804738] sd 5:0:0:0: [sdb] Write
> Protect is off
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.804760] sdb: sdb1
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.837230] sd 5:0:0:0: [sdb] Attached
> SCSI disk
> Mar 27 11:05:12 XPS-1 kernel: [ 7264.837377] sd 5:0:0:0: Attached scsi
> generic sg2 type 0
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.513967] kjournald starting. Commit
> interval 5 seconds
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.513995] EXT3-fs warning: maximal
> mount count reached, running e2fsck is recommended
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.515031] EXT3 FS on sdb1, internal
> journal
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.515040] EXT3-fs: recovery complete.
> Mar 27 11:05:13 XPS-1 kernel: [ 7265.522316] EXT3-fs: mounted filesystem
> with ordered data mode.
>
> Now if I do anything that causes reads from the drive (in this case
> "du -sh /media/disk", I get the following in the log:
>
> Mar 27 11:05:48 XPS-1 kernel: [ 7300.911188] usb 2-2: reset high speed
> USB device using ehci_hcd and address 7
> Mar 27 11:05:49 XPS-1 kernel: [ 7301.173948] sd 5:0:0:0: [sdb]...

[idistech (gary-idistech)]

I had the problem re-occur recently, but it was fixed with an updated/improved cable. No problems with 12.04 and the right cable now. The original software problem that I experienced prior to kernels 3.x seems to have gone. :-)

[Rolf Leggewie (r0lf)]

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".