Ubuntu
linux package

lucid beta 1 fails to mount external USB 3.0 storage

Bug #549107 reported by Peter B P
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Rebooting system and attaching storage (WD MyBook 3.0 1 TB external hard drive, attached via USB 3.0 connection. Drive attaches, mounts and transfers data fine in Karmic).

System log follows:

Mar 26 21:30:37 winter9 kernel: [ 393.410251] usb 9-2: new SuperSpeed USB device using xhci_hcd and address 2
Mar 26 21:30:37 winter9 kernel: [ 393.431704] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
Mar 26 21:30:37 winter9 kernel: [ 393.432074] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
Mar 26 21:30:37 winter9 kernel: [ 393.432450] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
Mar 26 21:30:37 winter9 kernel: [ 393.432825] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
Mar 26 21:30:37 winter9 kernel: [ 393.433091] usb 9-2: configuration #1 chosen from 1 choice
Mar 26 21:30:37 winter9 kernel: [ 393.434233] scsi11 : SCSI emulation for USB Mass Storage devices
Mar 26 21:30:42 winter9 kernel: [ 398.434109] scsi 11:0:0:0: Direct-Access WD My Book 3.0 1123 1006 PQ: 0 ANSI: 4
Mar 26 21:30:42 winter9 kernel: [ 398.434563] sd 11:0:0:0: Attached scsi generic sg8 type 0
Mar 26 21:30:42 winter9 kernel: [ 398.434683] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
Mar 26 21:30:42 winter9 kernel: [ 398.436647] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
Mar 26 21:30:42 winter9 kernel: [ 398.438285] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
Mar 26 21:30:47 winter9 kernel: [ 398.440003] sd 11:0:0:0: [sdh] Spinning up disk....ready
Mar 26 21:30:47 winter9 kernel: [ 403.421574] sd 11:0:0:0: [sdh] 1953519616 512-byte logical blocks: (1.00 TB/931 GiB)
Mar 26 21:30:47 winter9 kernel: [ 403.421712] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
Mar 26 21:30:47 winter9 kernel: [ 403.422115] sd 11:0:0:0: [sdh] Write Protect is off
Mar 26 21:30:47 winter9 kernel: [ 403.422588] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
Mar 26 21:30:47 winter9 kernel: [ 403.422992] sdh: sdh1
Mar 26 21:30:47 winter9 kernel: [ 403.463139] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
Mar 26 21:30:47 winter9 kernel: [ 403.463611] sd 11:0:0:0: [sdh] Attached SCSI disk
Mar 26 21:30:47 winter9 kernel: [ 403.660543] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
Mar 26 21:30:47 winter9 kernel: [ 403.751212] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
Mar 26 21:30:50 winter9 kernel: [ 406.750281] usb 9-2: USB disconnect, address 2
Mar 26 21:30:50 winter9 kernel: [ 406.772594] usb 9-2: Device not responding to set address.
Mar 26 21:30:51 winter9 kernel: [ 406.980153] usb 9-2: Device not responding to set address.

(repeated about 20 times)

Mar 26 21:31:08 winter9 kernel: [ 424.300296] usb 9-2: Device not responding to set address.
Mar 26 21:31:08 winter9 kernel: [ 424.520134] usb 9-2: Device not responding to set address.
Mar 26 21:32:07 winter9 kernel: [ 483.520017] xhci_hcd 0000:04:00.0: Timeout while waiting for a slot

System log spam ends because I've run through ubuntu-bug storage and followed its instructions to unplug and replug the device; if I hadn't the 'Device not responding to set address' would have continued indefinately. (AS this happens, the HD activity LED is flashing constantly).

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: peter 1796 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 22'
   Mixer name : 'VIA VT1708S'
   Components : 'HDA:11060397,10438346,00100000'
   Controls : 36
   Simple ctrls : 20
Date: Fri Mar 26 21:31:00 2010
DistroRelease: Ubuntu 10.04
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=621422d8-40d5-4a6b-8e28-8c06a13b2d01
HotplugNewDevices:

HotplugNewMounts:

InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux-image-2.6.32-17-generic 2.6.32-17.26
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=ab34a929-f1b8-4f0b-b36f-269e1363ec83 ro quiet splash
ProcEnviron:
 LANG=en_DK.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Regression: Yes
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
RfKill:

SourcePackage: linux
Symptom: storage
TestedUpstream: No
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
Uname: Linux 2.6.32-17-generic x86_64
dmi.bios.date: 05/22/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0405
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5QL/EPU
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0405:bd05/22/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Peter B P (peterbp) wrote :
Revision history for this message
Peter B P (peterbp) wrote :

Update afther the last week's worth of updates:

Plugging the same USB 3.0 device now tends to result in a kernel panic, booting my out my my X session and leaving me at a generic, purple Ubuntu logo screen, with no response to keyboard or mouse input whatsoever.

Booting the system with same unit plugged in on power-on leaves a frozen system after entering user name and password (frozen cursor, no reponse to keyboard input).

Revision history for this message
Peter B P (peterbp) wrote :

Update:

I'm happy to say that today's batch of updates (I'm guessing hdparm update) has made my USB 3.0 storage work fine again.

Thanks!

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Peter,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Peter B P (peterbp) wrote :

Heya Jeremy.

I'm just tested it with v2.6.34-rc5-lucid; oddly, the drive isn't even registered anymore.

System log gives no indication that plugging it in is even noticed by the system (as log excerpt in original post shows). The drive does not show in disk utility either.

tags: removed: needs-upstream-testing
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Peter,
    This isn't, by chance, a multi-input port (i.e USB/HDMI) is it?

Thanks!

~JFo

Revision history for this message
Peter B P (peterbp) wrote :

Hey Jeremy,

No. The port is a pure USB 3.0 port on a Western Digital PCIe expansion card that came with the hard drive.

It's tested to work fine in Ubuntu Karmic and an earlier release of Lucid (Beta 2 + some updates). I'm puzzled why it's broken again.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Peter,
    I see. I've assigned importance to this and the Triaged status. I've got it slated to be looked at by one of the kernel devs so hopefully we can see what changed.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Revision history for this message
Peter B P (peterbp) wrote :

Update: On starting my machine (with the new mainline kernel) today, the hard drive is recognized, but only operates at USB 2.0 speeds. System log reads:

May 1 20:07:07 winter9 kernel: [ 11.980787] scsi 9:0:0:0: Direct-Access WD My Book 3.0 1123 1006 PQ: 0 ANSI: 4
May 1 20:07:07 winter9 kernel: [ 11.981254] sd 9:0:0:0: Attached scsi generic sg7 type 0
May 1 20:07:07 winter9 kernel: [ 11.982576] sd 9:0:0:0: [sdg] 1953519616 512-byte logical blocks: (1.00 TB/931 GiB)
May 1 20:07:07 winter9 kernel: [ 11.982726] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
May 1 20:07:07 winter9 kernel: [ 11.983330] sd 9:0:0:0: [sdg] Write Protect is off
May 1 20:07:07 winter9 kernel: [ 11.984127] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
May 1 20:07:07 winter9 kernel: [ 11.984686] sdg: sdg1
May 1 20:07:07 winter9 kernel: [ 12.014286] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
May 1 20:07:07 winter9 kernel: [ 12.018158] sd 9:0:0:0: [sdg] Attached SCSI disk
May 1 20:08:19 winter9 kernel: [ 83.319472] EXT4-fs (sdg1): mounted filesystem with ordered data mode

I see nothing about it switching back to OHCI (which would explain why I'm only getting speeds of a USB 2.0 disk)...

Revision history for this message
Peter B P (peterbp) wrote :

Update:

Also tested with the RC6 mainline kernel release as of 30/april.

I'm still not getting consistent behavior from the drive. Sometimes its is available to the system, sometimes not.

Revision history for this message
Peter B P (peterbp) wrote :

Update: I seem to get consistent behavior now.

Status is that if the drive is already hooked up to the PC on boot, it mounts and runs fine at the expected USB 3.0 speed.

If the drive is not hooked up at the time of boot, plugging it in when the PC is on will have no effect, and it wont even show anything in the system log.

Running latest Lucid kernel (2.6.32-22-generic).

Summarizing: It works, it's just the plug detection or functionality that doesn't.

Revision history for this message
Peter B P (peterbp) wrote :

Update:

Scratch last comment, I cannot get reliable behavior out of the USB 3.0 drive.

For the better part of the last month, it has seemingly mounted and functioned okay. Until today, where, upon booting my workstation, I had several hangs, either during the boot process, or immediately after, on logging into my accoutn and the gnoem desktop being loaded, shortly after, the screen froze totally, cursor included.

This happened multiple times, until i had luck in getting to view the system log, which revealed this (much more than quoted, for brevity reasons):

Jun 21 12:00:01 winter9 kernel: [ 24.670147] usb 9-2: Device not responding to set address.
Jun 21 12:00:01 winter9 kernel: [ 24.880306] usb 9-2: Device not responding to set address.
Jun 21 12:00:02 winter9 kernel: [ 25.090158] usb 9-2: Device not responding to set address.
Jun 21 12:00:02 winter9 kernel: [ 25.300304] usb 9-2: Device not responding to set address.
Jun 21 12:00:02 winter9 kernel: [ 25.510144] usb 9-2: Device not responding to set address.
Jun 21 12:00:05 winter9 kernel: [ 28.040279] usb 9-2: Device not responding to set address.
Jun 21 12:00:05 winter9 kernel: [ 28.250160] usb 9-2: Device not responding to set address.
Jun 21 12:00:05 winter9 kernel: [ 28.460289] usb 9-2: Device not responding to set address.
Jun 21 12:00:05 winter9 kernel: [ 28.670168] usb 9-2: Device not responding to set address.
Jun 21 12:00:05 winter9 kernel: [ 28.880311] usb 9-2: Device not responding to set address.
Jun 21 12:00:06 winter9 kernel: [ 29.090162] usb 9-2: Device not responding to set address.

etc.

Unplugging the hard drive allowed system to boot and run as normal.

I'm currently running lucid amd64 with proposed-updates.

Barrign hardware failure in the host adapter, I cannot explain this erratic behavior, but I will consider USB 3.0 hardware unrealiable for work use until further light is shed on this.

Jeremy Foshee (jeremyfoshee)
tags: removed: regression-potential
Revision history for this message
Jaakko Hartikainen (jaakko-hartikainen) wrote :

I can also confirm this. I have a USB3.0 WD MyBook 1.0 TB and if the drive is connected to USB 3.0 when booting, I get loads of these messages:

[ 2.532465] usb 9-2: Device not responding to set address.
[ 2.736033] usb 9-2: device not accepting address 2, error -71
[ 2.792052] hub 9-0:1.0: unable to enumerate USB device on port 2

USB mice and keyboards also totally hang randomly when this occurs, and the problem resolves after unplugging the myBook's USB cable. No errors when plugged in to USB 2.0 and other PC's, so it's not a hardware issue.

Motherboard: Gigabyte GA970UD3 (Etron EJ168 USB 3.0 controller)
Kernel: 3.2.0-35-generic AMD64

Revision history for this message
penalvch (penalvch) wrote :

Peter B P, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11.1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Peter B P (peterbp) wrote :

Christopher,

thank you for the reminder. I have progressed quite a bit beyond Lucid since I reported the bug, and I don't have the hardware that I used to test Lucid on anymore.

For what it's worth, I also have a suspicion that the problem in question was caused by the USB 3.0 adapter card from Western Digital, and not the operating system, but that is hard to say anything about at this point.

In any case, thank you for your attention.
-p

Revision history for this message
penalvch (penalvch) wrote :

Peter B P, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549107/comments/15 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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