Bug 1398485

Summary:	USB 3 flash drive in USB 3 hub not recognized
Product:	[Fedora] Fedora	Reporter:	sgiurgiu11
Component:	systemd	Assignee:	Orphan Owner <extras-orphan>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	25	CC:	extras-orphan, johannbg, jonathan, lnykryn, msekleta, muadda, ssahani, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 10:19:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description sgiurgiu11 2016-11-25 00:58:03 UTC

Description of problem:
Motherboard: ASUS P9X79 PRO with ASMedia ASM1042 USB 3.0 chipset
USB 3.0 hub : ANKER with VIA Labs, Inc. VL812 chipset

1. When I plug in a USB 3.0 flash drive into one of the ports of the 3.0 hub, the drive is not recognized at all. No messages at all in dmesg.

2. If I plug the same flash drive directly into one of the USB 3.0 ports in the back of the motherboard, the drive is recognized and mounted immediately.

3. If I plug a USB 2.0 drive into the USB 3.0 hub, the drive is recognized and mounted

4. If I plug the USB 3.0 flash drive into a USB 2.0 port (or hub) the drive is recognized and mounted

5. With the USB 3.0 drive plugged into the 3.0 hub, doing "cat /dev/bus/usb/006/003" causes the drive to be recognized and mounted. 

6. If I boot Fedora with the drive plugged in, it is recognized and mounted.

The USB 3.0 drive and the USB 3.0 hub work perfectly in FreeBSD and Windows on the same system. I actually have the hub for a long time now and it behaved like this from the beginning. It was even before Fedora 23.

Now, I have selected udev as the component to blame, but to be honest, I have no idea if that's the cause. It could be a different issue someplace else.
lsusb:

Bus 002 Device 008: ID 12ba:00ff Licensed by Sony Computer Entertainment America Rocksmith Guitar Adapter
Bus 002 Device 007: ID 04d9:2013 Holtek Semiconductor, Inc. Keyboard [Das Keyboard]
Bus 002 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 005: ID 046d:0a1f Logitech, Inc. G930
Bus 002 Device 004: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 003: ID 046d:c07d Logitech, Inc. G502 Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub -- my hub
Bus 006 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub -- my hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub -- my hub
Bus 005 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub -- my hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 046d:08ad Logitech, Inc. QuickCam Communicate STX
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


After I do the "cat" dance, dmesg shows proper device recognition:

[ 2171.533938] usb 6-2.4.4: new SuperSpeed USB device number 4 using xhci_hcd
[ 2171.556408] usb 6-2.4.4: New USB device found, idVendor=0951, idProduct=16a2
[ 2171.556412] usb 6-2.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2171.556415] usb 6-2.4.4: Product: DTR30G2
[ 2171.556418] usb 6-2.4.4: Manufacturer: Kingston
[ 2171.556420] usb 6-2.4.4: SerialNumber: 0018F30C0839BEB19179DD3F
[ 2171.559330] usb-storage 6-2.4.4:1.0: USB Mass Storage device detected
[ 2171.559996] scsi host9: usb-storage 6-2.4.4:1.0
[ 2172.650966] scsi 9:0:0:0: Direct-Access     Kingston DTR30G2          PMAP PQ: 0 ANSI: 6
[ 2172.652097] sd 9:0:0:0: Attached scsi generic sg5 type 0
[ 2172.976659] sd 9:0:0:0: [sdd] 30736384 512-byte logical blocks: (15.7 GB/14.7 GiB)
[ 2172.977778] sd 9:0:0:0: [sdd] Write Protect is off
[ 2172.977783] sd 9:0:0:0: [sdd] Mode Sense: 23 00 00 00
[ 2172.978918] sd 9:0:0:0: [sdd] No Caching mode page found
[ 2172.978925] sd 9:0:0:0: [sdd] Assuming drive cache: write through                                                                                                            
[ 2173.004332]  sdd: sdd1 sdd2 sdd3
[ 2173.008239] sd 9:0:0:0: [sdd] Attached SCSI removable disk

Version-Release number of selected component (if applicable):
Name        : systemd-udev
Version     : 231
Release     : 10.fc25


How reproducible:
Always. USB 3.0 flash drive plugged into USB 3.0 hub is not recognized until I poke it with a "cat /dev/bus/usb/006/003" command.

Steps to Reproduce:
1. Insert USB 3.0 flash drive into USB 3.0 hub port

Actual results:
Nothing. Not a peep from dmesg.

Expected results:
The drive to be recognized, given a device and ideally mounted.

Additional info:

Comment 1 sgiurgiu11 2016-12-23 03:57:21 UTC

As of the latest update of Fedora 25, it seems that problem is solved:

Linux <pc> 4.8.14-300.fc25.x86_64 #1 SMP Mon Dec 12 16:31:04 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

systemd-231-10.fc25.x86_64

Comment 2 Fedora End Of Life 2017-11-16 19:30:24 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:19:56 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.