ExpressCard type USB3.0 adapter does not function properly

Bug #1446798 reported by Donatas Glodenis
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

ExpressCard type USB3.0 adapter for laptop does not function properly with the current kernel of Vivid: drives attached to it do not get reported by the system as attached and cannot get mounted.

The expressCard adapter does work on a 14.04 install on another hardware (32 bit), giving 3x read spead from an external USB 3.0 drive. The expressCard socket also works on this particular computer - tested with expressCard 3G modem.

The adapter in question: 2 Port USB3.0 expressCard, UNEC UPD720202 Chip
 see here for description http://www.amazon.co.uk/SuperSpeed-compatible-transfer-Notebook-internal/dp/B00K49TNUU

Upon inserting the adapter dmesg displays this information:

[ 9095.296966] pci 0000:05:00.0: [1912:0015] type 00 class 0x0c0330
[ 9095.297051] pci 0000:05:00.0: reg 0x10: [mem 0x00000000-0x00001fff 64bit]
[ 9095.297426] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
[ 9095.304643] pci 0000:05:00.0: BAR 0: assigned [mem 0xf1c00000-0xf1c01fff 64bit]
[ 9095.304738] pci 0000:05:00.0: enabling device (0000 -> 0002)
[ 9095.305384] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 9095.305406] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 3
[ 9095.311315] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 9095.311327] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 9095.311335] usb usb3: Product: xHCI Host Controller
[ 9095.311342] usb usb3: Manufacturer: Linux 3.19.0-15-generic xhci-hcd
[ 9095.311349] usb usb3: SerialNumber: 0000:05:00.0
[ 9095.311881] hub 3-0:1.0: USB hub found
[ 9095.311957] hub 3-0:1.0: 2 ports detected
[ 9095.312407] xhci_hcd 0000:05:00.0: xHCI Host Controller
[ 9095.312422] xhci_hcd 0000:05:00.0: new USB bus registered, assigned bus number 4
[ 9095.314347] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 9095.314357] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 9095.314365] usb usb4: Product: xHCI Host Controller
[ 9095.314372] usb usb4: Manufacturer: Linux 3.19.0-15-generic xhci-hcd
[ 9095.314379] usb usb4: SerialNumber: 0000:05:00.0
[ 9095.314895] hub 4-0:1.0: USB hub found
[ 9095.314973] hub 4-0:1.0: 2 ports detected

dmesg upon inserting usb3.0 external hard drive (ADATA) into one of the ports of ExpressCard adapter:

[ 9176.313022] usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 9176.334581] usb 4-2: New USB device found, idVendor=125f, idProduct=a13a
[ 9176.334591] usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 9176.334597] usb 4-2: Product: NH13
[ 9176.334601] usb 4-2: Manufacturer: ADATA
[ 9176.334606] usb 4-2: SerialNumber: 12041076060229000009
[ 9176.336521] usb-storage 4-2:1.0: USB Mass Storage device detected
[ 9176.336972] scsi host9: usb-storage 4-2:1.0

BUT the drive does not appear as an attached device.

If I boot the computer with the expresscard inserted and the external drive attached, I do get to see it in the new device notifier, but I still cannot mount it.

Besides, trying to use the adapter results in the computer being unable to suspend (the screen blackens out, but the machine does not go to sleep) and problems shutting it down.

I would gladly provide any required information and do more tests if needed, just tell me what to do.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dg 1435 F.... pulseaudio
CurrentDesktop: KDE
Date: Tue Apr 21 20:53:33 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-04-05 (15 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150403)
MachineType: LENOVO 4298A12
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=bb4491a9-508a-492c-8fd7-9707fe9818ef ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-15-generic N/A
 linux-backports-modules-3.19.0-15-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UdevLog: Error: [Errno 2] Toks failas ar aplankas neegzistuoja: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET54WW (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4298A12
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET54WW(1.24):bd10/18/2011:svnLENOVO:pn4298A12:pvrThinkPadX220Tablet:rvnLENOVO:rn4298A12:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4298A12
dmi.product.version: ThinkPad X220 Tablet
dmi.sys.vendor: LENOVO

Revision history for this message
Donatas Glodenis (dgvirtual) 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 v4.0 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/v4.0-vivid/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: regression-update
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Donatas Glodenis (dgvirtual) wrote :

Installed the suggested upstream kernel, and the bug also affects it. So I marked the bug with the tag bug-exists-upstream.

Also tried to install the latest Utopic kernel to test with it. Test failed: the Utopic kernel did not recognize not only the usb drive attached through the expressCard adapter, it did not recognize the drive when attached to normal USB2 port.

tags: added: bug-exists-upstream
description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
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
Donatas Glodenis (dgvirtual) wrote :

Well, I could perhaps do the steps describet in source [0], but I am just a hobbyist Linux user and - at a loss determining, which kernel mailing list I should send the information to. Any ideas?

Revision history for this message
Donatas Glodenis (dgvirtual) wrote :

~jsalisbury , I need your input before I proceed sending bug report to kernel. Once I started reporting the bug I noticed, that on the new kernel the problem is even worse: the expressCard is recognized (I see output in dmesg), but once I attach the external drive to it nothing is reported in dmesg, it is not reported in lsusb, etc.

So, I would say, either the problem is different using the upstream kernel (regression got even worse), or the upstream kernel is not "compatible" with Ubuntu Vivid enough to see the problem the same way (now, otherwise the system seems to be behaving just fine, everything is working with the new kernel...)

What do you think?

Revision history for this message
Donatas Glodenis (dgvirtual) wrote :

Here is the upstream bug report: https://bugzilla.kernel.org/show_bug.cgi?id=97801

Please note that I noticed while testing with upstream kernel, that the bug manifests itself only on hotplug of the adapter. If I boot with it, the adapter functions as expected.

tags: added: kernel-bug-reported-upstream
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.