Hi Mathias,
I re-tried if this issue exists with linux-4.4-rc7 and I reproduced it. Actually, with ASM-based USB3-to-SATA dongle instead of the one with Prolific chipset. I suspect it is maybe more prone to happen or even specific to my back side USB3.0 port of my Dell Vostro 3550 laptop, in contrast to the second USB3.0 port located on right hand side. However, BOTH are wired to same TexasInstruments host chip so it does not make much sense to me.
In the http://195.113.57.32/~mmokrejs/Aukey-4.4.rc7.tar.bzip2 file (156kB) you can see I collected initial lsusb -v and dmesg, then connected the Aukey hub to the rear port and connected to it a HDD drive via the ASMedia dongle. That failed with a LED of the particular Aukey HUB port blinking. I tried another port of the HUB, also the LED started blinking. Then I connected the HUB (with the dongle connected) to the second USB 3.0 port of my laptop (located on rear, no rear) and it worked (LED stopped blinking but was stably turned on and filesystem was mounted). I collected final dmesg and lsusb -v.
I hope this time the extra kernel debug and usbmon trace is more helpful.
Thank you for your help,
Martin
Mathias Nyman wrote:
On 25.11.2015 00:09, Martin MOKREJŠ wrote:
Hi,
I have relatively new 13port USB 3.0 HUB based on VIAlabs 812 chipset with two power-only charging ports: 1x1.5A and 1x2.4A (AUKEY CB-H16, from Amazon). Sometimes, the hub (actually four 4-port hubs stitched together) chokes and all it's LEDs start blinking. I found it is caused by one device, which is a USB3 to SATA dongle:
PremiumCord KU3IDE3 Prolific PL2773 + JMD330 0x067b:0x2773 (1.00)
Now, I caught usbmon trace to show it is not recognized. Interestingly, the linux usb driver is unable to recognize any other device on that port. Even unplugging the fooled Aukey hub does not help, I have to reboot. Seems linux kernel is too much trying to enumerate some device on that port. But that seems a secondary issue to me. I can hook to the hub 12 other USB3 to SATA dongles (all based on ASMedia chip) and they all work fine.
If I connect the PremiumCord KU3IDE3 dongle via similar, VIA810 4-port hub with FW9.60 to the same laptop port it works fine. The laptop has TexasInstruments USB3 chip.
When I boot into Win7 the Aukey hub and PremiumCord KU3IDE3 play nicely together.
Thank you for you help,
Martin
An excerpt from the looping part of usbmon log show port link state seems to be Inactive.
This should be done on serious error condition to operate the link.
fff880408d47798 383464649 S Ci:2:001:0 s a3 00 0000 0001 0004 4 <
ffff880408d47798 383464681 C Ci:2:001:0 0 4 = c3027000
If I read the bits correctly the get port status request replies with status
connected, enabled, powered and link state is Inactive.
change bits were set for reset, bh reset and link state.
ffff880408d47798 383464717 S Co:2:001:0 s 23 01 0014 0001 0000 0
ffff880408d47798 383464731 C Co:2:001:0 0 0
ffff880408d47798 383464744 S Co:2:001:0 s 23 01 001d 0001 0000 0
ffff880408d47798 383464754 C Co:2:001:0 0 0
ffff880408d47798 383464766 S Co:2:001:0 s 23 01 0019 0001 0000 0
ffff880408d47798 383464776 C Co:2:001:0 0 0
ffff880408d47798 383464788 S Co:2:001:0 s 23 01 0010 0001 0000 0
ffff880408d47798 383464798 C Co:2:001:0 0 0
The previuis lines show hub cleared the changed port features
(reset change, bh reset change, link state change and port connect)
ffff880408d47798 383464810 S Ci:2:001:0 s a3 00 0000 0001 0004 4 <
ffff880408d47798 383464819 C Ci:2:001:0 0 4 = c3020000
the next get poer status still shows link is in inactive state
ffff880408d47798 383464831 S Co:2:001:0 s 23 03 001c 0001 0000 0
ffff880408d47798 383464843 C Co:2:001:0 0 0
Try to warm reset, Hub: Set port feature 1c = BH_PORT_RESET
Maybe enabling usb core and xhci debugging could show better what is going on
echo -n 'module xhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control
echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control
-Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
