external USB hard drive disconnects

Bug #349767 reported by Steve Conklin
218
This bug affects 37 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Won't Fix
Medium
Unassigned
Lucid
Won't Fix
Undecided
Unassigned

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 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

Revision history for this message
Steve Conklin (sconklin) wrote :
Revision history for this message
Steve Conklin (sconklin) wrote :

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"

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Steve Conklin (sconklin) wrote :

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

Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :

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.

Revision history for this message
Steve Conklin (sconklin) wrote :

David,

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

Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote : apport-collect data

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

Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
tags: added: apport-collected
Revision history for this message
Robbie Williamson (robbiew) wrote :

Steve, does this still happen with Lucid Alpha 3?

Revision history for this message
Jerone Young (jerone) wrote :

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.

Revision history for this message
Jerone Young (jerone) wrote :

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

Revision history for this message
Fabus (fabian-gebert-hh) wrote :

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.

Revision history for this message
Thorsten Hesemeyer (thorsten-hesemeyer) wrote :

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

Revision history for this message
Thorsten Hesemeyer (thorsten-hesemeyer) wrote :

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

Revision history for this message
Herco van Brug (hercovanbrug) wrote :
Download full text (4.0 KiB)

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: ...

Read more...

Revision history for this message
Herco van Brug (hercovanbrug) wrote :

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.

Revision history for this message
Fabus (fabian-gebert-hh) wrote :

see #580983

Revision history for this message
Bogdan (bogdan-veringioiu) wrote :

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

Revision history for this message
Bogdan (bogdan-veringioiu) wrote : AlsaDevices.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : AplayDevices.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : BootDmesg.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : Card0.Amixer.values.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : Card0.Codecs.codec.0.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : CurrentDmesg.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : IwConfig.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : Lspci.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : PciMultimedia.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : ProcCpuinfo.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : ProcInterrupts.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : ProcModules.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : UdevDb.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : UdevLog.txt
Revision history for this message
Bogdan (bogdan-veringioiu) wrote : WifiSyslog.txt
33 comments hidden view all 113 comments
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

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.

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :
Revision history for this message
Budoc (budoc) wrote :
Download full text (14.8 KiB)

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] ...

Revision history for this message
NeilGreenwood (neil-greenwood) wrote : Re: [Bug 349767] Re: external USB hard drive disconnects
Download full text (16.2 KiB)

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...

Revision history for this message
John B (johnb-ca) wrote :

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!

Revision history for this message
John B (johnb-ca) wrote :

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...

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

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.

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

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?

description: updated
Revision history for this message
usbdevice (rook-e) wrote :

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

Revision history for this message
Jools Wills (jools) wrote :

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)

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

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?

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Andrew B (andrew-berridge) wrote :

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 ;-)

Revision history for this message
Matej Kenda (matejken) wrote :

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.

Revision history for this message
Matej Kenda (matejken) wrote :

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.

Revision history for this message
Seth Forshee (sforshee) wrote :

@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.

Revision history for this message
Matej Kenda (matejken) wrote :

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.

Revision history for this message
jochenb (jochen-2) wrote :

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

Revision history for this message
Matej Kenda (matejken) wrote :

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.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

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.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

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"

Changed in linux (Ubuntu Lucid):
status: New → Confirmed
Revision history for this message
Matej Kenda (matejken) wrote :
Revision history for this message
Matej Kenda (matejken) wrote :
Revision history for this message
Matej Kenda (matejken) wrote :

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?

Revision history for this message
Gustavo (paolo-nino) wrote :

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.

Revision history for this message
Matej Kenda (matejken) wrote :

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?

Revision history for this message
Gustavo (paolo-nino) wrote : Re: [Bug 349767] Re: external USB hard drive disconnects
Download full text (8.7 KiB)

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...

Read more...

Revision history for this message
Gustavo (paolo-nino) wrote :
Download full text (15.3 KiB)

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: [...

Revision history for this message
Gustavo (paolo-nino) wrote :

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!

Revision history for this message
Gustavo (paolo-nino) wrote :

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

Revision history for this message
Gustavo (paolo-nino) wrote :

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?

Revision history for this message
Matej Kenda (matejken) wrote :

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

Revision history for this message
Gustavo (paolo-nino) wrote :
Download full text (11.4 KiB)

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...

Revision history for this message
DiegoRivera (diego-rivera) wrote :

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.

Changed in linux:
status: Confirmed → Invalid
Changed in linux:
status: Invalid → Fix Released
Revision history for this message
Václav Šmilauer (eudoxos) wrote :

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?

Revision history for this message
Wayde Nie (niew) wrote :

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.

Revision history for this message
avinash (avinashreddyk) wrote :

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.

Revision history for this message
Gustavo (paolo-nino) wrote :
Download full text (8.8 KiB)

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]...

Read more...

Revision history for this message
idistech (gary-idistech) wrote :

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. :-)

Revision history for this message
Rolf Leggewie (r0lf) wrote :

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".

Changed in linux (Ubuntu Lucid):
status: Confirmed → Won't Fix
Displaying first 40 and last 40 comments. View all 113 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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