External USB3 hard drive fails to connect (JMicron bridge 152d:0569)

Bug #1378401 reported by Matej Kenda
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

A Hitachi 2.5" disk in USB 3 disk enclosure with JMicron chip fails to be connected on Ubuntu Trusty.

The same system was booted with Utopic Unicorn Beta 2 to verify whether newer kernel resolves the problem. Unfortunatelly it does not.

The disk was properly recognised only the first time it was attached.

[ 346.790756] usb 4-4: new SuperSpeed USB device number 3 using xhci_hcd
[ 346.807293] usb 4-4: New USB device found, idVendor=152d, idProduct=0569
[ 346.807301] usb 4-4: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 346.807304] usb 4-4: Product: USB to ATA/ATAPI Bridge
[ 346.807307] usb 4-4: Manufacturer: JMicron
[ 346.807310] usb 4-4: SerialNumber: 4A3337343030383448584B595845
[ 348.477947] usb-storage 4-4:1.0: USB Mass Storage device detected
[ 348.478225] scsi7 : usb-storage 4-4:1.0
[ 348.478395] usbcore: registered new interface driver usb-storage
[ 348.588835] usbcore: registered new interface driver uas
[ 349.475655] scsi 7:0:0:0: Direct-Access Hitachi HTS727575A9E364 PQ: 0 ANSI: 5
[ 349.476095] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 349.476243] sd 7:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
[ 349.476734] sd 7:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 349.477219] sd 7:0:0:0: [sdb] Asking for cache data failed
[ 349.477224] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 349.760792] sdb: sdb1
[ 349.762218] sd 7:0:0:0: [sdb] Attached SCSI disk
[ 350.097878] EXT4-fs (sdb1): recovery complete
[ 350.098248] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 350.293120] systemd-hostnamed[6253]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[ 396.016083] usb 4-4: USB disconnect, device number 3

Further attempts failed, regardless of how the disk was attached:

* directly to powered USB 3 port on the laptop
* to USB 3 port in laptop dock
* via USB 2 hub with external power

[ 409.808551] usb 3-1.1: new high-speed USB device number 4 using xhci_hcd
[ 409.897277] usb 3-1.1: New USB device found, idVendor=152d, idProduct=0569
[ 409.897284] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 409.897287] usb 3-1.1: Product: USB to ATA/ATAPI Bridge
[ 409.897290] usb 3-1.1: Manufacturer: JMicron
[ 409.897293] usb 3-1.1: SerialNumber: 4A3337343030383448584B595845
[ 409.897953] usb-storage 3-1.1:1.0: USB Mass Storage device detected
[ 409.898260] scsi8 : usb-storage 3-1.1:1.0
[ 410.897754] scsi 8:0:0:0: Direct-Access Hitachi HTS727575A9E364 PQ: 0 ANSI: 5
[ 410.898406] sd 8:0:0:0: Attached scsi generic sg2 type 0
[ 410.898589] sd 8:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
[ 410.899099] sd 8:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 410.899549] sd 8:0:0:0: [sdb] Asking for cache data failed
[ 410.899555] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[ 411.509408] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd
[ 411.509446] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
[ 411.509453] usb 3-1.1: hub failed to enable device, error -22
[ 411.581221] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd
[ 411.581268] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
[ 411.581274] usb 3-1.1: hub failed to enable device, error -22
[ 411.653254] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd
[ 411.669800] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030f78a9c0
[ 411.669808] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88030f78aa08
[ 411.749480] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd
[ 411.749527] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
[ 411.749534] usb 3-1.1: hub failed to enable device, error -22
[ 411.821215] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd
[ 411.821256] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
[ 411.821262] usb 3-1.1: hub failed to enable device, error -22
[ 411.893315] usb 3-1.1: reset high-speed USB device number 4 using xhci_hcd
---
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 2655 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 2655 F.... pulseaudio
CasperVersion: 1.344
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: Hewlett-Packard HP EliteBook 8770w
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-17-generic N/A
 linux-backports-modules-3.16.0-17-generic N/A
 linux-firmware 1.134
Tags: utopic
Uname: Linux 3.16.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/08/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IAV Ver. F.43
dmi.board.name: 176C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 50.1C
dmi.chassis.asset.tag: CNU2429ZG3
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68IAVVer.F.43:bd10/08/2013:svnHewlett-Packard:pnHPEliteBook8770w:pvrA1008C11:rvnHewlett-Packard:rn176C:rvrKBCVersion50.1C:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8770w
dmi.product.version: A1008C11
dmi.sys.vendor: Hewlett-Packard

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 :
summary: - External USB3 JMicron hard drive fails to be connected
+ External USB3 hard drive fails to connect (JMicron bridge 152d:0569)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1378401

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.

Changed in linux (Ubuntu):
status: New → Incomplete
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.17 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.17-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Matej Kenda (matejken) wrote :

@Brad: Does the attached output from ubuntu-bug linux contain sufficient information or is it better to use apport-collect?

@Joseph: I booted from DVD. I'll try to make bootable flash disk and install latest kernel as you suggested.

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

apport information

tags: added: apport-collected utopic
description: updated
Revision history for this message
Matej Kenda (matejken) wrote : BootDmesg.txt

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

apport information

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

Latest 3.17 kernel was installed on Utopic to test this problem.

Behaviour is the same.

External HD is recognised only first one or two times after booting the system.

Similar errors as with previous kernels are reported in dmesg then. I noticed that they slightly differ if the disk is connected directly to USB 3 port or through USB 2 powered hub.

The disk in this enclosure works properly when connected to MacBook Pro laptop.

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

Attached dmesg output containing logs from attempts to use the drive.

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

Syslog with complete trace from boot on.

Matej Kenda (matejken)
tags: added: kernel-bug-exists-upstream
penalvch (penalvch)
tags: added: bios-outdated-f.50 trusty
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Matej Kenda (matejken) wrote :

Thanks, Christopher. I will update BIOS on the laptop and report the results.

I think that there are small chances that this would help, though because the same problem is reproducible on two other computers as well.

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

BIOS on the laptop was updated to version F.50 (the latest).

The behaviour is worst as with previous BIOS: the disk fails to connect even on the first attempt after booting.

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
68IAV Ver. F.50
08/04/2014

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

Behaviour was verified on utopic with Linux kernel 3.17:

$ uname -a
Linux utopic 3.17.0-031700-generic #201410060605 SMP Mon Oct 6 10:07:09 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
penalvch (penalvch) wrote :

Matej Kenda, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

tags: added: latest-bios-f.50
removed: bios-outdated-f.50
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Matej Kenda (matejken) wrote :
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.