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

Issue 776780 link

Starred by 1 user
Status: Fixed
Owner:
█ nxia@chromium.org
Last visit > 30 days ago
Closed: Oct 2017
Cc:
█ nxia@chromium.org
xiaochu@chromium.org
grundler@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

chromeos6-row2-rack20-host22: Persistent 'usb 1-5: device not accepting address 13, error -62'

Project Member Reported by groeck@chromium.org, Oct 20 2017 
Seen with the last couple of provisioning jobs on chromeos6-row2-rack20-host22:

ERR kernel: [  176.112836] usb 1-5: device not accepting address 12, error -62
2017-10-20T14:44:43.243048+00:00 INFO kernel: [  176.266058] usb 1-5: new full-speed USB device number 13 using xhci_hcd
2017-10-20T14:44:48.248719+00:00 ERR kernel: [  181.271668] xhci_hcd 0000:00:14.0: Command completion event does not match command
2017-10-20T14:44:48.248765+00:00 WARNING kernel: [  181.271748] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
2017-10-20T14:44:53.465441+00:00 WARNING kernel: [  186.487579] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
2017-10-20T14:44:53.666083+00:00 ERR kernel: [  186.688582] usb 1-5: device not accepting address 13, error -62
2017-10-20T14:44:53.666118+00:00 ERR kernel: [  186.688754] usb usb1-port5: unable to enumerate USB device

http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/873784-provision/
http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/872775-provision/

This also happened before, often resulting in a sequence of provision-reset-repair loop.

http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/867509-provision/

Comment 1 by groeck@chromium.org, Oct 20 2017 

Example for repeated reset/repair/provison jobs:

2017-10-20 00:51:07  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/870945-provision/
    2017-10-19 23:08:00  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/870057-repair/
    2017-10-19 23:07:31  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/870053-reset/
    2017-10-19 23:02:15  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869997-repair/
    2017-10-19 23:01:46  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869990-reset/
    2017-10-19 22:55:26  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869939-repair/
    2017-10-19 22:54:55  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869934-reset/
    2017-10-19 22:49:43  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869856-repair/
    2017-10-19 22:34:42  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869752-provision/
    2017-10-19 21:03:47  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869179-repair/
    2017-10-19 21:03:18  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869175-reset/
    2017-10-19 20:58:01  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869132-repair/
    2017-10-19 20:57:31  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869128-reset/
    2017-10-19 20:52:17  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869084-repair/
    2017-10-19 20:51:44  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869079-reset/
    2017-10-19 20:46:27  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869026-repair/
    2017-10-19 20:45:56  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/869008-reset/
    2017-10-19 20:40:46  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/868976-repair/
    2017-10-19 20:27:06  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/868842-provision/
    2017-10-19 18:37:28  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/867901-repair/
    2017-10-19 18:36:56  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/867893-reset/
    2017-10-19 18:31:40  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/867829-repair/
    2017-10-19 18:31:05  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/867818-reset/
    2017-10-19 18:25:49  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/867743-repair/
    2017-10-19 18:25:18  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/867736-reset/
    2017-10-19 18:20:11  OK http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/867668-repair/
    2017-10-19 18:04:39  -- http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos6-row2-rack20-host22/867509-provision/

Comment 2 by davidri...@chromium.org, Oct 20 2017

Cc: grundler@chromium.org

Comment 3 by groeck@chromium.org, Oct 20 2017

Owner: nxia@chromium.org

Comment 4 by nxia@chromium.org, Oct 20 2017 

I'll replace this dut. 

https://uberchromegw.corp.google.com/i/chromeos/builders/wizpig-paladin/builds/1265

But the failed provision job contains chrome crashes:

FAIL	----	verify.cros	timestamp=1508502834	localtime=Oct 20 05:33:54	Chrome failed to reach login. System services not running.

Which should be the reason of the provision failure?

Comment 5 by nxia@chromium.org, Oct 20 2017 

 crbug.com/776120  (merged to crbug.com/765686) should be the cause.

Comment 6 by nxia@chromium.org, Oct 20 2017

Status: Fixed (was: Untriaged)
moved out the dut and filed the fix ticket at b/68047721
►

Sign in to add a comment