Can't mount USB3 flash drive

Bug #1291081 reported by Michael
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

While trying to mount a USB3 flash drive I get errors like:

[ 88.961035] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
[ 88.976746] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88020f4465c0
[ 88.976757] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88020f446580
[ 88.977319] sd 6:0:0:0: [sdb] Unhandled error code
[ 88.977321] sd 6:0:0:0: [sdb]
[ 88.977323] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 88.977324] sd 6:0:0:0: [sdb] CDB:
[ 88.977325] Read(10): 28 00 00 00 12 53 00 00 f0 00
[ 88.977331] end_request: I/O error, dev sdb, sector 4691

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-17-generic 3.13.0-17.37
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michael 1943 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Mar 11 23:22:03 2014
InstallationDate: Installed on 2014-03-07 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140306)
MachineType: LENOVO 34481Y2
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=d6f1faeb-4441-407a-a989-97022eb7a6a6 ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-17-generic N/A
 linux-backports-modules-3.13.0-17-generic N/A
 linux-firmware 1.126
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: G6ETA3WW (2.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 34481Y2
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG6ETA3WW(2.63):bd02/19/2014:svnLENOVO:pn34481Y2:pvrThinkPadX1Carbon:rvnLENOVO:rn34481Y2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 34481Y2
dmi.product.version: ThinkPad X1 Carbon
dmi.sys.vendor: LENOVO

Revision history for this message
Michael (mig000) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc6-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Michael (mig000) wrote :

Appears to be fixed in 3.14.0-031400rc6-generic upstream.

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Michael (mig000) wrote :

Changing the tag to kernel-bug-exists-upstream as the problem actually reappeared with the 3.14.0-031400rc6-generic upstream kernel. I will attach new details / dmesg output.

tags: added: kernel-bug-exists-upstream
removed: kernel-fixed-upstream
Revision history for this message
Michael (mig000) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Michael (mig000) wrote :

Unfortunately I don't have access to the hardware anymore.

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

Other bug subscribers

Remote bug watches

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