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

Issue 797007 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ bmgordon@chromium.org
█ jrbarnette@chromium.org
█ martinroth@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: ----



Sign in to add a comment

provision failed on snappy-release:1301

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 21 2017 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of bmgordon@google.com

snappy-release:1301 failed

Builders failed on: 
- snappy-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/snappy-release/1301

ssh timed out during provisioning on the sanity HWTest.  right before the timeout, dmesg errors seem to suggest that the network card hung up and got restarted:

[  870.612713] i2c_designware i2c_designware.2: i2c_dw_handle_tx_abort: slave address not acknowledged (7bit mode)
[  982.607515] smsc95xx 1-4.1:1.0 eth0: hardware isn't capable of remote wakeup
[  982.651047] smsc95xx 1-4.1:1.0 eth0: hardware isn't capable of remote wakeup
[  982.651201] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  982.733640] smsc75xx 1-3:1.0 eth1: device_set_wakeup_enable error -22
[  985.856543] smsc75xx 1-3:1.0 eth1: link up, 1000Mbps, full-duplex, lpa 0xC1E1
[  990.634493] i2c_designware i2c_designware.2: i2c_dw_handle_tx_abort: slave address not acknowledged (7bit mode)

The immediately following repair job logged in with ssh and powerwashed the system without trouble:

http://cautotest/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row4-rack2-host1/1336082-repair/

Comment 1 by bmgordon@chromium.org, Dec 21 2017

Cc: -bmgordon@google.com martinroth@chromium.org jrbarnette@chromium.org bmgordon@chromium.org
Components: Infra>Client>ChromeOS
Labels: -Pri-2 Pri-3
Project Member

Comment 2 by sheriffbot@chromium.org, Dec 24

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment