xhci regression: usb 3.0 hdd disconnects immediately

[b3nmore]

On a fresh saucey installation (kernel 3.11), I can not use my external usb 3.0 hdd on usb 3.0 ports, it only works on usb 2 ports. kernel log shows, that it disconnects immediately after it is plugged in. Then it continues to connect and disconnect indefinitely (q.v. attached dmesg log):

[ 2623.116141] usb 3-5: new SuperSpeed USB device number 2 using xhci_hcd
[ 2623.132574] usb 3-5: New USB device found, idVendor=1058, idProduct=0740
[ 2623.132582] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 2623.132587] usb 3-5: Product: My Passport 0740
[ 2623.132591] usb 3-5: Manufacturer: Western Digital
[ 2623.132595] usb 3-5: SerialNumber: 575847314139315836343531
[ 2623.133533] usb-storage 3-5:1.0: USB Mass Storage device detected
[ 2623.133758] scsi7 : usb-storage 3-5:1.0
[ 2624.299678] usb 3-5: USB disconnect, device number 2
[ 2645.281554] scsi 7:0:0:0: Device offlined - not ready after error recovery
[ 2645.281727] usb 3-5: Set SEL for device-initiated U1 failed.
[ 2645.281730] usb 3-5: Set SEL for device-initiated U2 failed.
[ 2645.521559] usb 3-5: new SuperSpeed USB device number 3 using xhci_hcd
...

The same hw combination works with kernel 3.2 in precise, but not with 3.8 (see attachments below). I even tried 3.12 coming with trusty, but got the same log messages as with 3.11.
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: kiran 1633 F.... pulseaudio
 /dev/snd/controlC0: kiran 1633 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=5ea8b83e-6f6f-4e44-98f6-45ade2c2d6c3
InstallationDate: Installed on 2013-11-16 (7 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
IwConfig:
 p2p1 no wireless extensions.

 lo no wireless extensions.
MachineType: ASUS All Series
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic.efi.signed root=UUID=4fee8160-326f-4688-a0d9-22e158e70f45 ro
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-13-generic N/A
 linux-backports-modules-3.11.0-13-generic N/A
 linux-firmware 1.116
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy
Uname: Linux 3.11.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 06/28/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0410
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-G
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.:bvr0410:bd06/28/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

[b3nmore (b3nmore)]

Same drive on saucy when using the usb 2 port.

[b3nmore (b3nmore)]

Precise with kernel 3.2 succeeds to connect the drive on usb 3.0.

[b3nmore (b3nmore)]

lsusb -v output on 3.2 on usb 3.0 port.

[b3nmore (b3nmore)]

kernel log of a precise live system with kernel 3.8 failing to connect the drive on a usb 3.0 port.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1254261

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[b3nmore (b3nmore)]

apport information

[N1ck 7h0m4d4k15 (nicktux)]

Hello,

it seems a bit strange because the CurrentDmesg.txt (comment #9) doesn't show the problem. Also I have Trusty Tahr installed and a WD USB3.0 external HDD and I haven't such problems. Either I connect it to USB2.0 or 3.0 port.

It would be helpful if you provide additional information during the connection of HDD.

Open a terminal (CTRL+ALT+T) and write:

    watch -n1 "dmesg | tail -n 30"

then connect the HDD and post back here the lines will be produced.

Best Regards
 NikTh

[b3nmore (b3nmore)]

> It would be helpful if you provide additional information during the connection of HDD.

This should be in the log file attached to comment #1. If there are any further logs/test I could provide, please name them.

[N1ck 7h0m4d4k15 (nicktux)]

Hello,

have you tried the latest kernel ?
These are my results from the fresh updated Trusty Tahr. (kernel-3.12.0-4)

[b3nmore (b3nmore)]

Same failure with 3.12.0-4 from trusty daily live.

[b3nmore (b3nmore)]

Same with mainline kernel 3.13-rc1.

[N1ck 7h0m4d4k15 (nicktux)]

Can you please confirm that the filesystem of that disk is in a good condition ?

If it's NTFS then it would be better to check it with a Windows tool.

If it's linux filesystem (e.g. ext4) the you can use fsck tool.

Best Regards
   NikTh

[b3nmore (b3nmore)]

sudo fsck.ext4 -v /dev/sdc1
e2fsck 1.42 (29-Nov-2011)
BackupDisc: clean, 631430/61046784 files, 211311384/244182016 blocks

sudo fsck.ext4 -vf /dev/sdc1
e2fsck 1.42 (29-Nov-2011)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

  631430 inodes used (1.03%)
    6303 non-contiguous files (1.0%)
     249 non-contiguous directories (0.0%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 629529/208
211311384 blocks used (86.54%)
       0 bad blocks
      27 large files

  580948 regular files
   48495 directories
       0 character device files
       0 block device files
       0 fifos
      17 links
    1970 symbolic links (1677 fast symbolic links)
       8 sockets
--------
  631438 files

[N1ck 7h0m4d4k15 (nicktux)]

Hello,

it would be good for the bug's life-cycle to open a report upstream in order to inform the USB 3.0 developers

https://bugzilla.kernel.org/

Add a link here (when this done) and also add a link in the upstream report to point in this bug report.

My disk (comment #22) it's NTFS filesystem, so I cannot confirm something on ext4 filesystem. Maybe this is due to the filesystem combined with the USB 3.0 support.

Thanks for this report.

Best Regards
    NikTh

[b3nmore (b3nmore)]

Filed an upstream report under:
https://bugzilla.kernel.org/show_bug.cgi?id=65631

[b3nmore (b3nmore)]

As a last resort I upgraded the bios/uefi of the mainboard (B85M-G BIOS 0410 -> B85M-G BIOS 0703) and now it works.

Funny though, that 3.2 managed to circumvent whatever the bios messed up. Anyway, sorry for the noise.

[Peter Davey (ubhntu)]

I too found myself here because I have been experiencing this same problem with an Asus B85M-G motherboard. I'll check the BIOS revision tomorrow and report back if an upgrade fixes it.