Kernel Does not recognize some USB 3.0 hard drives

[[e-mail]]

Running Ubuntu 16,04 in VMware Fusion on an Apple Mac Book Pro, when connecting a USB 3.0 external drive it does not mount. It seems to choke at the kernel level. dmesg shows incomplete loading, and never gets a device assigned.

This works correctly in Ubuntu 14.04 on a VM and vanilla kernel 4.4.13.

Confirmed bug on different HW with kernel 4.4.10 imac arch linux bare metal

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-24-generic 4.4.0-24.43
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: john 1836 F.... pulseaudio
CurrentDesktop: XFCE
Date: Sat Jun 11 07:31:18 2016
HibernationDevice: RESUME=UUID=814c9f61-7a4e-43bf-8a22-32628d812842
InstallationDate: Installed on 2014-07-20 (691 days ago)
InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
IwConfig:
 ens33 no wireless extensions.

 lo no wireless extensions.
MachineType: VMware, Inc. VMware Virtual Platform
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=7828d00a-d744-4ecf-a5f4-9f6fe0006ff6 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-generic N/A
 linux-firmware 1.157
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-05-19 (22 days ago)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7-rc1 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'.

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/v4.7-rc3-yakkety/

[[e-mail] (jkeelercox)]

Per Joseph's recommendation :
"Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7-rc1 kernel[0]."

Installed latest upstream kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc3-yakkety/
and booted.
Still exhibits bug
dmesg shows the same.

[penalvch (penalvch)]

<email address hidden>, to clarify, did this issue not occur in a Ubuntu kernel earlier than 4.4.0-24-generic?

[[e-mail] (jkeelercox)]

Ubuntu 16.04, kernel 4.2.0-16 and 4.4.0-24, will not mount the drive.

Ubuntu 14.04 : kernel 3.13.0-24 successfully mounts the drive.

[[e-mail] (jkeelercox)]

Christopher M. Penalver (penalvch),
Yeah they are both me, sorry for the confusion ... so many go* da** accounts and so many logins.
You want to make the next internet billion?, solve that problem ...
... I will delete, this is an older account.
Will deactivating the account delete the comments I have already made?

[[e-mail] (jkeelercox)]

Per penalvch's recommendation :

Installed latest upstream kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc6-yakkety/
and booted.
Still exhibits bug
dmesg :

[ 28.340550] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 28.362325] usb 2-1: New USB device found, idVendor=0bc2, idProduct=ab24
[ 28.362329] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 28.362331] usb 2-1: Product: BUP Slim BK
[ 28.362332] usb 2-1: Manufacturer: Seagate
[ 28.362333] usb 2-1: SerialNumber: NA7LYM08

I also tried enabling uas from the modprobe.d/ blacklist.conf, per google searching.
It gets further but still will not mount the drive
I confirmed this behavior is consistent with with rc3 and 4.4.0-24.

[ 88.574108] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 88.595434] usb 2-1: New USB device found, idVendor=0bc2, idProduct=ab24
[ 88.595440] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 88.595443] usb 2-1: Product: BUP Slim BK
[ 88.595444] usb 2-1: Manufacturer: Seagate
[ 88.595446] usb 2-1: SerialNumber: NA7LYM08
[ 88.626473] scsi host33: uas
[ 88.626755] usbcore: registered new interface driver uas
[ 88.628897] scsi 33:0:0:0: Direct-Access Seagate BUP Slim BK 0302 PQ: 0 ANSI: 6
[ 88.655532] sd 33:0:0:0: Attached scsi generic sg4 type 0
[ 88.656083] sd 33:0:0:0: [sdd] Spinning up disk...
[ 89.682395] .ready
[ 89.683600] sd 33:0:0:0: [sdd] 3907029167 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 89.683605] sd 33:0:0:0: [sdd] 4096-byte physical blocks
[ 90.882771] sd 33:0:0:0: [sdd] Write Protect is off
[ 90.882779] sd 33:0:0:0: [sdd] Mode Sense: 4f 00 00 00
[ 90.883914] sd 33:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 90.885177] sd 33:0:0:0: tag#0 data cmplt err -71 uas-tag 1 inflight: CMD
[ 90.885183] sd 33:0:0:0: tag#0 CDB: Inquiry 12 01 00 00 40 00
[ 121.937783] sd 33:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[ 121.937792] sd 33:0:0:0: tag#0 CDB: Inquiry 12 01 00 00 40 00
[ 121.937909] scsi host33: uas_eh_bus_reset_handler start
[ 122.052871] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 122.194535] usb 2-1: device firmware changed
[ 124.818870] usb usb2-port1: Could not disable after 2000 ms
[ 124.819015] scsi host33: uas_post_reset: alloc streams error -19 after reset
[ 124.819210] usb 2-1: USB disconnect, device number 2
[ 130.770888] EXT4-fs (sdc1): recovery complete
[ 130.770993] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[ 132.966110] EXT4-fs (sdc3): mounted filesystem with ordered data mode. Opts: (null)

[penalvch (penalvch)]

<email address hidden>, to clarify, which kernel were you using when this worked in Ubuntu 14.04?

[[e-mail] (jkeelercox)]

Using Ubuntu 14.04 : kernel 3.13.0-24 successfully mounts the drive.

In the original post : "This works correctly in Ubuntu 14.04 on a VM and vanilla kernel 4.4.13."
Should have read : "This works correctly in Ubuntu 14.04 on a VM using kernel 3.13.0-24.
Another data point, possibly relevant, in a different HW configuration (No VM, older 2010 Apple iMAC, USB 2.0 logic board, same Hard Drive): Arch Linux using kernel 4.4.10 showed the bug, but upgrading to Arch kernel 4.4.13 remedied the issue"

[penalvch (penalvch)]

<email address hidden>, the next step is to fully commit bisect from kernel 3.13 to 4.4 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your help.

[[e-mail] (jkeelercox)]

Still working it but here is the status on the bisect ...
Ubuntu 14.04 Latest Kernel = Good
Ubuntu 14.10 latest kernel = Bad
 Breakdown of distro 14.10
    kernel version 3.13.0-24.46 = good
    kernel version 3.13.0-24.47 = good
    kernel version 3.15.0-1.3 = bad, next into the commit tree

[[e-mail] (jkeelercox)]

Update : Still working this ... it is taking longer than I had hoped.

I feel like a dummy but I am having issues building the older kernels from git.

The 4.4.13 and the 4.7rc6 built and ran, no problem

but during the bisect building the 3.13.0-24.47 to 3.15.0-1.3 kernels have been an issue.
Using an Ubuntu 16.04 base OS, the kernel Makefile needed to be changed, setting CC=gcc-4.8, or it would not compile, complaining about gcc5 header files missing.

after changing the makefile, it then built ok but when the .deb kernel-image packages are installed and the system rebooted the OS dies immediately after grub loading initramfs, with a message from the vm manager saying the host os has disabled the cpu.

I then tried rebuilding on an older (slower!) 14.04 machine and that worked, built and ran fine if i scp'd .deb's over to the VM and tested.

Now the bisect has brought me to 3.15 and the debian/rules folder has been deleted,
which is what I was using here : https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
I am now looking at this :
https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
which doesn't require the debian/ folder.
Any suggestions?, I am going about this the correct way?

[[e-mail] (jkeelercox)]

Same issue:
https://bbs.archlinux.org/viewtopic.php?id=183190
https://bbs.archlinux.org/viewtopic.php?pid=1428782#p1428782

workaround that seems to work for all versions is to
add a conf file to /etc/modprobe.d, with this line
    options usb-storage quirks=0bc2:ab24:u

not done with the bisect got down to commit ea1990c3796 (bad) and Tag : Ubuntu 3.13.0-24.47 (good)

[[e-mail] (jkeelercox)]

Finished bisect :

f50a4968deb7bf38c46f5baf62db9431a099531a is the first bad commit
commit f50a4968deb7bf38c46f5baf62db9431a099531a
Author: Hans de Goede <email address hidden>
Date: Mon Oct 28 10:48:04 2013 +0000

    uas: Add Hans de Goede as uas maintainer

    At the kernel-summit Sarah Sharp asked me if I was willing to become the
    uas maintainer. I said yes, and here is a patch to make this official.

    Also remove Matthew Wilcox and Sarah Sharp as maintainers at their request.

    I've also added myself to the module's author tag, so that if people look there
    rather then in maintainers they will know they should bug me about uas too.

    Signed-off-by: Hans de Goede <email address hidden>
    Signed-off-by: Sarah Sharp <email address hidden>

:100644 100644 c6d0e93eff62d700443b93dff01120d36d2ce52a fc536bc743008f1f78f419d94fd50c3d91919f38 M MAINTAINERS
:040000 040000 d80df04bea7cb66bcabf94dc7367cd03c809f9cb fd22777fee4ce38189376255affddddaa6fa7dca M drivers

[[e-mail] (jkeelercox)]

Sorry disregard last comment ... bug in a script, I was one commit off:

dc88608dba784f902b3127fd68d0c4f92a532cd0 is the first bad commit
commit dc88608dba784f902b3127fd68d0c4f92a532cd0
Author: Gerd Hoffmann <email address hidden>
Date: Fri Sep 13 13:27:15 2013 +0200

    uas: remove BROKEN

    xhci streams support is fixed, unblock usb attached scsi.

    Signed-off-by: Gerd Hoffmann <email address hidden>
    Signed-off-by: Hans de Goede <email address hidden>
    Signed-off-by: Sarah Sharp <email address hidden>

:040000 040000 4e5651f811a9b0b321f5be6b812a594a38baaae2 d80df04bea7cb66bcabf94dc7367cd03c809f9cb M drivers

[[e-mail] (jkeelercox)]

It looks like the offending commit only removes the BROKEN dependency from the Kconfig uas build.

Not entirely sure the consequnecs of this , does this simply tell the kernel to use uas ?
Maybe need to dig in and look at the low level protocols and id what is choking up the driver, per arch linux links in comment 16.

[penalvch (penalvch)]

<email address hidden>, in order to upstream this, could you please test the latest mainline kernel (4.7-rc7) and advise to the results?

[[e-mail] (jkeelercox)]

Per penalvch's recommendation :

Installed latest upstream kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc7
and booted.
Still exhibits bug

[penalvch (penalvch)]

<email address hidden>, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Gerd Hoffman, Hans de Goede, and Sarah Sharp CC linux-usb and linux-scsi)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.

[Robert Gebis (rjgebis-w)]

I have the same issue under 16.04 LTS running under Parallels 11. Under 14.04 it works well.

Here is my 16.04 LTS dmesg

[ 17.098137] random: nonblocking pool is initialized
[ 84.186235] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 84.201216] usb 4-1: New USB device found, idVendor=174c, idProduct=1351
[ 84.201219] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 84.201220] usb 4-1: Product: USB3.1 Device
[ 84.201221] usb 4-1: Manufacturer: Generic
[ 84.201222] usb 4-1: SerialNumber: 00000000000000000000
[ 84.729194] usbcore: registered new interface driver usb-storage
[ 84.733541] scsi host8: uas
[ 84.733606] usbcore: registered new interface driver uas

Here is my 14.04 LTS dmsge

[ 41.530114] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 41.546540] usb 4-1: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 41.547080] usb 4-1: New USB device found, idVendor=174c, idProduct=1351
[ 41.547083] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 41.547085] usb 4-1: Product: USB3.1 Device
[ 41.547086] usb 4-1: Manufacturer: Generic
[ 41.547087] usb 4-1: SerialNumber: 00000000000000000000
[ 41.572631] usb-storage 4-1:1.0: USB Mass Storage device detected
[ 41.572710] scsi8 : usb-storage 4-1:1.0
[ 41.572751] usbcore: registered new interface driver usb-storage
[ 42.572273] scsi 8:0:0:0: Direct-Access ASMT 2135 0 PQ: 0 ANSI: 6
[ 42.572749] sd 8:0:0:0: Attached scsi generic sg2 type 0
[ 42.576130] sd 8:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 42.578385] sd 8:0:0:0: [sdb] Write Protect is off
[ 42.578388] sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 42.579646] sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 42.855427] sdb: sdb1
[ 42.886689] sd 8:0:0:0: [sdb] Attached SCSI disk