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

Issue 756763 link

Starred by 1 user
Status: Fixed
Owner:
sadolfsson@chromium.org
Closed: May 2018
Cc:
lndmrk@chromium.org
smbar...@chromium.org
█ wirebrand@chromium.org
sadolfsson@chromium.org
harpreet@chromium.org
█ katierh@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Atrus fails to be enumerated if not connected directly to Guado and SiS fails to be enumerated regardless how it is connected to Guado.

Project Member Reported by mzhuo@chromium.org, Aug 18 2017 
Chrome Version: (copy from chrome://version)
R61-9765.21.0

What steps will reproduce the problem?
(1)Reboot Guado
(2)Toggle GPIO 60+ times. Shut down power, wait for 2 seconds, bring power back.Then wait for about 90 seconds to repeat.
(3) After it found Atrus has problem to be enumerated.

Topology:
---------
Atrus -----Lindy 8m---- Huddly
      ----- Lindy 8m ------Plugable -----Atrus + Mimo

Debug
-----
tried: 
     unplug/plug usb cable on plugable, 
     unplug/plug power for plugable, 
     unplug/plug usb cable from atrus to plugable, 
     unplug/plug usb cable from usb analyzer to guado
     unplug/plug power for analyzer
     unplug/plug lindy 8m cable 
     bypass plugable, still keep lindy 8m cable which is connected to Atus
     Connect plugable directly to Guado
     unplug/plug usb cable from Atrus to Plugable
None of the above make Atrus work. 

Finally connect Atrus directly to Guado. it works. But when we disconnect and  reconnect Atrus to Guado via Plugable it is not working again. 
Connecting Logitech, mouse to plugable, both work. Displaylink in Mimo also works via plugable. 

     

What is the expected result?
===========================
Atrus always work.

What happens instead?
Atrus fails to be enumerated. 

Please use labels and text to provide additional information.
====================================================================
2017-08-17T15:17:15.329106-07:00 INFO kernel: [17478.049665] usb 1-2: New USB device found, idVendor=058f, idProduct=6254
2017-08-17T15:17:15.329141-07:00 INFO kernel: [17478.049689] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
2017-08-17T15:17:30.671106-07:00 ERR kernel: [17493.403956] usb 1-2.1: device descriptor read/64, error -110
2017-08-17T15:17:30.772078-07:00 ERR kernel: [17493.504967] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 18.
2017-08-17T15:17:45.913079-07:00 ERR kernel: [17508.658274] usb 1-2.1: device descriptor read/64, error -110
2017-08-17T15:17:46.014082-07:00 ERR kernel: [17508.759262] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 14.
2017-08-17T15:17:51.100130-07:00 ERR kernel: [17513.849348] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:17:56.517087-07:00 ERR kernel: [17519.270739] usb 1-2.1: device not accepting address 78, error -62
2017-08-17T15:18:01.596102-07:00 ERR kernel: [17524.353830] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:18:07.013119-07:00 ERR kernel: [17529.775204] usb 1-2.1: device not accepting address 79, error -62
2017-08-17T15:18:07.013152-07:00 ERR kernel: [17529.775302] hub 1-2:1.0: unable to enumerate USB device on port 1
2017-08-17T15:18:07.160094-07:00 INFO kernel: [17529.923141] usb 1-2.3: New USB device found, idVendor=17e9, idProduct=016b
2017-08-17T15:18:07.160120-07:00 INFO kernel: [17529.923170] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2017-08-17T15:18:07.160124-07:00 INFO kernel: [17529.923192] usb 1-2.3: Product: MIMO VUE HD
2017-08-17T15:18:07.160127-07:00 INFO kernel: [17529.923207] usb 1-2.3: Manufacturer: DisplayLink
2017-08-17T15:18:08.404717-07:00 ERR mtpd[1059]: LIBMTP_Detect_Raw_Devices failed with 5
2017-08-17T15:47:20.275057-07:00 WARNING kernel: [19284.454762] udevd[16172]: Process '/opt/displaylink/udev.sh /dev usb-001-080-DisplayLink_MIMO_VUE_HD_MTACP17070005 /dev/bus/usb/001/080' failed with exit code 1.
2017-08-17T15:47:34.551091-07:00 INFO kernel: [19298.742656] usb 1-2: New USB device found, idVendor=2109, idProduct=2813
2017-08-17T15:47:34.551119-07:00 INFO kernel: [19298.742680] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
2017-08-17T15:47:34.551124-07:00 INFO kernel: [19298.742698] usb 1-2: Product: USB2.0 Hub
2017-08-17T15:47:34.925092-07:00 INFO kernel: [19299.116867] usb 1-2.1: New USB device found, idVendor=2109, idProduct=2813
2017-08-17T15:47:34.925119-07:00 INFO kernel: [19299.116892] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
2017-08-17T15:47:34.925124-07:00 INFO kernel: [19299.116910] usb 1-2.1: Product: USB2.0 Hub
2017-08-17T15:47:50.173148-07:00 ERR kernel: [19314.376699] usb 1-2.2: device descriptor read/64, error -110
2017-08-17T15:47:50.274093-07:00 ERR kernel: [19314.477516] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 10.
2017-08-17T15:48:05.511138-07:00 ERR kernel: [19329.727037] usb 1-2.2: device descriptor read/64, error -110
2017-08-17T15:48:05.612161-07:00 ERR kernel: [19329.827953] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 31.
2017-08-17T15:48:10.732106-07:00 ERR kernel: [19334.952034] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:48:16.150116-07:00 ERR kernel: [19340.374442] usb 1-2.2: device not accepting address 85, error -62
2017-08-17T15:48:21.276095-07:00 ERR kernel: [19345.504551] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:48:26.693095-07:00 ERR kernel: [19350.925910] usb 1-2.2: device not accepting address 86, error -62
2017-08-17T15:48:26.693119-07:00 ERR kernel: [19350.926111] hub 1-2:1.0: unable to enumerate USB device on port 2
2017-08-17T15:48:41.848088-07:00 ERR kernel: [19366.093410] usb 1-2.3: device descriptor read/64, error -110
2017-08-17T15:48:41.949083-07:00 ERR kernel: [19366.194276] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
2017-08-17T15:48:57.104085-07:00 ERR kernel: [19381.361768] usb 1-2.3: device descriptor read/64, error -110
2017-08-17T15:48:57.205114-07:00 ERR kernel: [19381.462601] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
2017-08-17T15:49:07.701079-07:00 ERR kernel: [19391.967065] usb 1-2.3: device not accepting address 89, error -62
2017-08-17T15:49:12.779228-07:00 ERR kernel: [19397.050224] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:49:18.197074-07:00 ERR kernel: [19402.471573] usb 1-2.3: device not accepting address 90, error -62
2017-08-17T15:49:18.197093-07:00 ERR kernel: [19402.471761] hub 1-2:1.0: unable to enumerate USB device on port 3
2017-08-17T15:49:19.573205-07:00 INFO kernel: [19403.849284] usb 1-2.1.1: New USB device found, idVendor=046d, idProduct=082d
2017-08-17T15:49:19.573233-07:00 INFO kernel: [19403.849312] usb 1-2.1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=1
2017-08-17T15:49:19.573237-07:00 INFO kernel: [19403.849333] usb 1-2.1.1: Product: HD Pro Webcam C920
2017-08-17T15:49:35.019090-07:00 ERR kernel: [19419.307486] usb 1-2.1.2: device descriptor read/64, error -110
2017-08-17T15:49:35.120115-07:00 ERR kernel: [19419.408271] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 8.
2017-08-17T15:49:50.275115-07:00 ERR kernel: [19434.575733] usb 1-2.1.2: device descriptor read/64, error -110
2017-08-17T15:49:50.376109-07:00 ERR kernel: [19434.676592] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 9.
2017-08-17T15:49:55.467168-07:00 ERR kernel: [19439.772692] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:50:00.885141-07:00 ERR kernel: [19445.194053] usb 1-2.1.2: device not accepting address 94, error -62
2017-08-17T15:50:05.963187-07:00 ERR kernel: [19450.277168] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:50:11.381094-07:00 ERR kernel: [19455.698554] usb 1-2.1.2: device not accepting address 95, error -62
2017-08-17T15:50:11.381123-07:00 ERR kernel: [19455.698821] hub 1-2.1:1.0: unable to enumerate USB device on port 2
2017-08-17T15:50:11.544104-07:00 INFO kernel: [19455.861937] usb 1-2.1.3: New USB device found, idVendor=058f, idProduct=6254
2017-08-17T15:50:11.544131-07:00 INFO kernel: [19455.861961] usb 1-2.1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
2017-08-17T15:50:11.687840-07:00 ERR cras_server[4456]: USB card: vendor:046d, product:082d, serial num:96CD4B9F, checksum:23ccc40b
2017-08-17T15:50:11.860914-07:00 ERR rtanalytics[2843]: E0817 15:50:11.860898       2 rtanalytics_manager.cc:240] Unable to find video device with this context: Huddly GO: Huddly GO overview
2017-08-17T15:50:16.760622-07:00 ERR cras_server[4456]: hw_params: Input/output error: rate: 16000, ret_rate: 16000, channel: 2, format: 2
2017-08-17T15:50:16.761079-07:00 ERR kernel: [19461.083212] 91:3:1: usb_set_interface failed (-110)
2017-08-17T15:50:21.761504-07:00 ERR cras_server[4456]: hw_params: Input/output error: rate: 16000, ret_rate: 16000, channel: 2, format: 2
2017-08-17T15:50:21.761557-07:00 ERR cras_server[4456]: Enable HD Pro Webcam C920: USB Audio:2,0 failed, rc = -5
2017-08-17T15:50:21.762074-07:00 ERR kernel: [19466.088180] 91:3:1: usb_set_interface failed (-110)
2017-08-17T15:50:21.783668-07:00 ERR cras_server[4456]: fetch err: -32 for 1e
2017-08-17T15:50:21.802651-07:00 ERR rtanalytics[2843]: E0817 15:50:21.802629       2 rtanalytics_manager.cc:240] Unable to find video device with this context: Huddly GO: Huddly GO overview
2017-08-17T15:50:22.500234-07:00 ERR rtanalytics[2843]: E0817 15:50:22.500217       2 rtanalytics_manager.cc:240] Unable to find video device with this context: Huddly GO: Huddly GO overview
2017-08-17T15:50:26.765552-07:00 ERR cras_server[4456]: hw_params: Input/output error: rate: 16000, ret_rate: 16000, channel: 2, format: 2
2017-08-17T15:50:26.765621-07:00 ERR cras_server[4456]: Init HD Pro Webcam C920: USB Audio:2,0 failed, rc = -5
2017-08-17T15:50:26.766082-07:00 ERR kernel: [19471.096262] 91:3:1: usb_set_interface failed (-110)
2017-08-17T15:50:26.877138-07:00 ERR kernel: [19471.207119] usb 1-2.1.3.1: device descriptor read/64, error -110
2017-08-17T15:50:26.978086-07:00 ERR kernel: [19471.308168] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 28.
2017-08-17T15:50:42.120071-07:00 ERR kernel: [19486.462459] usb 1-2.1.3.1: device descriptor read/64, error -110
2017-08-17T15:50:42.221090-07:00 ERR kernel: [19486.563539] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 30.
2017-08-17T15:50:47.307162-07:00 ERR kernel: [19491.654574] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:50:52.726103-07:00 ERR kernel: [19497.076953] usb 1-2.1.3.1: device not accepting address 99, error -62
2017-08-17T15:50:57.803160-07:00 ERR kernel: [19502.159066] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:51:03.221114-07:00 ERR kernel: [19507.580446] usb 1-2.1.3.1: device not accepting address 100, error -62
2017-08-17T15:51:03.221133-07:00 ERR kernel: [19507.580527] hub 1-2.1.3:1.0: unable to enumerate USB device on port 1
2017-08-17T15:51:03.381097-07:00 INFO kernel: [19507.740954] usb 1-2.1.3.3: New USB device found, idVendor=17e9, idProduct=016b
2017-08-17T15:51:03.381124-07:00 INFO kernel: [19507.740984] usb 1-2.1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2017-08-17T15:51:03.381129-07:00 INFO kernel: [19507.741006] usb 1-2.1.3.3: Product: MIMO VUE HD
2017-08-17T15:51:03.381132-07:00 INFO kernel: [19507.741019] usb 1-2.1.3.3: Manufacturer: DisplayLink
2017-08-17T15:51:18.725110-07:00 ERR kernel: [19523.097162] usb 1-2.1.4: device descriptor read/64, error -110
2017-08-17T15:51:18.826073-07:00 ERR kernel: [19523.198054] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 21.
2017-08-17T15:51:33.980102-07:00 ERR kernel: [19538.364508] usb 1-2.1.4: device descriptor read/64, error -110
2017-08-17T15:51:34.081082-07:00 ERR kernel: [19538.465428] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
2017-08-17T15:51:39.163208-07:00 ERR kernel: [19543.552492] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:51:44.581136-07:00 ERR kernel: [19548.973887] usb 1-2.1.4: device not accepting address 104, error -62
2017-08-17T15:51:49.659193-07:00 ERR kernel: [19554.057009] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:51:55.077086-07:00 ERR kernel: [19559.478358] usb 1-2.1.4: device not accepting address 105, error -62
2017-08-17T15:51:55.077109-07:00 ERR kernel: [19559.478600] hub 1-2.1:1.0: unable to enumerate USB device on port 4
2017-08-17T15:51:56.404896-07:00 ERR mtpd[1059]: LIBMTP_Detect_Raw_Devices failed with 5
2017-08-17T15:52:21.413084-07:00 ERR kernel: [19585.835758] usb 1-2.3: device descriptor read/64, error -110
2017-08-17T15:52:21.514085-07:00 ERR kernel: [19585.936755] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 26.
2017-08-17T15:52:36.669089-07:00 ERR kernel: [19601.104161] usb 1-2.3: device descriptor read/64, error -110
2017-08-17T15:52:36.770084-07:00 ERR kernel: [19601.205062] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
2017-08-17T15:52:41.851209-07:00 ERR kernel: [19606.291204] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:52:47.269137-07:00 ERR kernel: [19611.712560] usb 1-2.3: device not accepting address 109, error -62
2017-08-17T15:52:52.347183-07:00 ERR kernel: [19616.795645] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-08-17T15:52:57.765127-07:00 ERR kernel: [19622.217006] usb 1-2.3: device not accepting address 110, error -62
2017-08-17T15:52:57.765166-07:00 ERR kernel: [19622.217286] hub 1-2:1.0: unable to enumerate USB device on port 3
2017-08-17T16:09:10.338360-07:00 ERR chrom

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

Log files are uploaded to https://drive.google.com/corp/drive/u/1/folders/0B8sYeJbsz9zKSHBMQV8xZ2pYZkk. 
Pls ask for permission.

Comment 1 by mzhuo@chromium.org, Aug 18 2017

Cc: wirebrand@chromium.org sadolfsson@chromium.org katierh@chromium.org

Comment 2 by mzhuo@chromium.org, Aug 18 2017 

localhost ~ # lsusb -t                                                                                                                                                                                     
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    |__ Port 2: Dev 63, If 0, Class=Video, Driver=uvcvideo, 5000M
    |__ Port 2: Dev 63, If 1, Class=Video, Driver=uvcvideo, 5000M
    |__ Port 2: Dev 63, If 2, Class=Video, Driver=uvcvideo, 5000M
    |__ Port 2: Dev 63, If 3, Class=Video, Driver=uvcvideo, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
    |__ Port 2: Dev 81, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 82, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 91, If 0, Class=Video, Driver=uvcvideo, 480M
            |__ Port 1: Dev 91, If 1, Class=Video, Driver=uvcvideo, 480M
            |__ Port 1: Dev 91, If 2, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 1: Dev 91, If 3, Class=Audio, Driver=snd-usb-audio, 480M
            |__ Port 3: Dev 96, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 3: Dev 101, If 0, Class=Vendor Specific Class, Driver=udl, 480M
    |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
localhost ~ # cat /etc/lsb-release                                                                                                                                                                         
CHROMEOS_RELEASE_APPID={8AA6D9AC-6EBC-4288-A615-171F56F66B4E}
CHROMEOS_BOARD_APPID={8AA6D9AC-6EBC-4288-A615-171F56F66B4E}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
DEVICETYPE=CHROMEBOX
CHROMEOS_RELEASE_BUILDER_PATH=guado-release/R61-9765.21.0
GOOGLE_RELEASE=9765.21.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BOARD=guado
CHROMEOS_RELEASE_BUILD_NUMBER=9765
CHROMEOS_RELEASE_BRANCH_NUMBER=21
CHROMEOS_RELEASE_CHROME_MILESTONE=61
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=9765.21.0 (Official Build) dev-channel guado test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_VERSION=9765.21.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
localhost ~ #

Comment 3 by mzhuo@chromium.org, Aug 18 2017

Cc: harpreet@chromium.org

Comment 4 by mzhuo@chromium.org, Aug 18 2017

Summary: Atrus and SiS controller fails to be enumerated if connected via Lindy 8m cable or Plugable USB hub (was: Atrus fails to be enumerated if connected via Lindy 8m cable or Plugable USB hub)
Swap a new Mimo, connect it directly to Guado. Hit the same issue. 
Connect the original Mimo to another Guado. both Display and SiS are up. 
So seems both SiS and Atrus have same issue. 
However, DisplayLink does not have issue. 
Also connecting 2 Mimos to Guado, one directly connected to Guado, one via Plugable ( no lindy cable), both has displayLink work, but SiS controller does not work. 
SiS on both Mimo work fine on another Guado ( 100.104.43.222 ).
atrus-2-mimo.tgz
3.1 MB Download

Comment 5 by lndmrk@chromium.org, Aug 21 2017

Cc: lndmrk@chromium.org

Comment 6 by katierh@chromium.org, Aug 22 2017

Labels: M-61
Owner: smbar...@chromium.org

Comment 7 by mzhuo@chromium.org, Aug 23 2017

Components: OS>Kernel

Comment 8 by choonc@google.com, Aug 28 2017

Owner: sadolfsson@chromium.org

Comment 9 by mzhuo@chromium.org, Aug 29 2017

Summary: Atrus and SiS controller fails to be enumerated if not connected directly to Guado (was: Atrus and SiS controller fails to be enumerated if connected via Lindy 8m cable or Plugable USB hub)

Comment 10 by mzhuo@chromium.org, Aug 29 2017 

Summary: 
======================================================================
Both Mimo and Atrus are connected to Plugable hub via Lindy 8m cable. AFter cutting/restoring power by toggling gpio a few times Atrus and SiS fail to be enumerated although DisplayLink works fine. 
After hitting the probem, 
Connected Atrus directly to Guado, it works.
Connected Mimo directly to Guado SiS fails too. 
Connected Mimo and Atrus to other Guado all works.

Comment 11 by mzhuo@chromium.org, Aug 29 2017

Summary: Atrus fails to be enumerated if not connected directly to Guado and SiS fails to be enumerated regardless how it is connected to Guado. (was: Atrus and SiS controller fails to be enumerated if not connected directly to Guado)

Comment 12 by mzhuo@chromium.org, May 21 2018

Status: Fixed (was: Untriaged)
This problem does not happen any more which could be due to new fw, or newly added linux patches and etc.
►

Sign in to add a comment