New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 797218 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

USB3 hub is missing after several replugs of docking station to USB3 or USB-C ports of Snappy Chromebook

Reported by adam.kal...@displaylink.com, Dec 22 2017

Issue description

Chrome OS Version: 64.0.3282.24 (Official Build) dev (64-bit)
Chrome OS Platform: 10176.13.1 (Official Build) dev-channel snappy

Steps To Reproduce:
(1) Boot CrOS
(2) Login as user (also reproducible on guest)
(3) Attach HP Travel Docking station HP USB Travel Docking Station to USBA port of Chromebook
(4) Unplug Docking station
(5) Check output of lsusb; 
(6) Keep repeating steps (3)-(5) until failure is present

Expected Result:
After attaching docking station its all components (especially USB Hubs of docking station USB3 and USB2 part) should be visible by the ChromeOS.
After calling lsusb in crosh I am expecting to see after each replug:
Bus 001 Device 007: ID 048d:1165 Integrated Technology Express, Inc. IT1165 Flash Controller
Bus 002 Device 002: ID 03f0:a01d Hewlett-Packard  <------------- USB3 part of the hub of docking station
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 18d1:5014 Google Inc. 
Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
Bus 001 Device 003: ID 0bda:57d6 Realtek Semiconductor Corp. 
Bus 001 Device 006: ID 03f0:0255 Hewlett-Packard <------------- USB2 part of the hub of docking station
Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Actual Result:
After couple replugs (correct number of replugs is vary) docking station to the Chromebook USB3 part of hub on dokcing station is gone from the system and not present to the user. Actual ouptut of lsusb at failure state:
Bus 001 Device 009: ID 048d:1165 Integrated Technology Express, Inc. IT1165 Flash Controller
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 18d1:5014 Google Inc. 
Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
Bus 001 Device 003: ID 0bda:57d6 Realtek Semiconductor Corp. 
Bus 001 Device 008: ID 03f0:0255 Hewlett-Packard <------------- only USB2 part of the hub of docking station is visible
Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


How frequently does this problem reproduce? Always

What is the impact to the user, and is there a workaround? 
User is missing all downstreams components attached to the USB3 docking station. As external display(s), Etherenet and Audio part of docking station are connected to USB3 (downstream) port user is missing all of them. This docking station got also exposed USB3 port for the user and any USB device (hi or super speed) is not recognized by the ChromeOS.
Workaround which can be applied is to unbind and bind USB controller; In crosh as root:
cd /sys/bus/pci/drivers/xhci_hcd/
echo -n XXXX\:XX\:XX.X > unbind
echo -n XXXX\:XX\:XX.XC > bind

Please provide any additional information below. Attach a screen shot or
log if possible.
Problem is present on Snappy platform and HP USB Travel Docking Station (P/N 839033-001) for USB3.0 connextivity on both USB3 ports on Chromebook.
Problem is present on Snappy platform and HP USB Travel Docking Station (P/N 839032-001) for USB-C connextivity on both USB-C ports on Chromebook.

Attaching CrOS logs at the moment of failure.

 
debug-logs_20171222-094908
81.5 KB View Download

Comment 1 by vsu...@google.com, Dec 22 2017

Components: IO>USB Infra>Platform
Components: -IO>USB -Infra>Platform OS>Kernel
Owner: vpalatin@chromium.org
Is this in your jurisdiction?

Comment 4 by vpalatin@google.com, Jan 17 2018

I have tried to order one of them: HP USB-C Travel Dock (aka Dock T0K29AA)
but I will have a look, this kind of investigation is kind of long and it's low on my priority list (particularly given the vendor cooperation on previous similar issues)
Have you been able to get the dock?

If we think this is something in the Intel side we can try to bring some of them in as well.

Comment 6 by vpalatin@google.com, Feb 23 2018

> Have you been able to get the dock?

Yes I finally got one.

> If we think this is something in the Intel side we can try to bring some of them in as well.

I don't know, the half-corrupted log provided in the bug just shows that if you hammer hard enough by disconnecting immediately after connection during the mass storage enumeration, sometimes the kernel is late to detect the USB3.0 disconnect and it does not happen before the reconnection.
it's not so good, but definitely a low priority item.
Cc: vpalatin@chromium.org tbroch@chromium.org
Owner: ----
Status: Available (was: Unconfirmed)

Sign in to add a comment