New issue
Advanced search Search tips

Issue 735132 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 735121



Sign in to add a comment

servo repair fails in /usr/share/vboot/bin/set_gbb_flags.sh 0 on servo

Project Member Reported by pprabhu@chromium.org, Jun 20 2017

Issue description

This another failure mode of servo repair.

Example: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos4-row13-rack2-host8/3604889-repair/20171706022453/debug/

Symptom:
06/17 02:27:50.287 INFO |        servo_host:0595| servo host chromeos4-row13-rack2-host8-servo does not require an update.
06/17 02:27:50.482 DEBUG|          ssh_host:0286| Running (ssh) '/usr/share/vboot/bin/set_gbb_flags.sh 0'
06/17 02:27:52.324 ERROR|             utils:0298| [stderr] flashrom v0.9.4  : f15c2fa : May 13 2017 03:58:01 UTC on Linux 4.4.4 (armv7l)
06/17 02:27:52.334 ERROR|             utils:0298| [stderr] flashrom v0.9.4  : f15c2fa : May 13 2017 03:58:01 UTC on Linux 4.4.4 (armv7l)
06/17 02:27:55.242 DEBUG|             utils:0298| [stdout] Calibrating delay loop... OK.
06/17 02:27:55.258 ERROR|             utils:0298| [stderr] delay loop is unreliable, trying to continue No EEPROM/flash device found.
06/17 02:27:55.259 ERROR|             utils:0298| [stderr] Note: flashrom can never write if the flash chip isn't found automatically.
06/17 02:27:55.397 ERROR|            repair:0449| Repair failed: Wait for update, then reboot servo host.
Traceback (most recent call last):
  File "/usr/local/autotest/client/common_lib/hosts/repair.py", line 447, in _repair_host
    self.repair(host)
  File "/usr/local/autotest/server/hosts/servo_repair.py", line 318, in repair
    super(_ServoRebootRepair, self).repair(host)
  File "/usr/local/autotest/server/hosts/repair.py", line 68, in repair
    host.run('/usr/share/vboot/bin/set_gbb_flags.sh 0')
  File "/usr/local/autotest/server/hosts/servo_host.py", line 319, in run
    return super(ServoHost, self).run(**run_args)
  File "/usr/local/autotest/site-packages/chromite/lib/metrics.py", line 306, in wrapper
    return fn(*args, **kwargs)
  File "/usr/local/autotest/server/hosts/ssh_host.py", line 297, in run
    ssh_failure_retry_ok)
  File "/usr/local/autotest/server/hosts/ssh_host.py", line 252, in _run
    raise error.AutoservRunError("command execution error", result)
AutoservRunError: command execution error
* Command: 
    /usr/bin/ssh -a -x  -o ControlPath=/tmp/_autotmp_LeUpwYssh-master/socket
    -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
    BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=180 -o
    ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22
    chromeos4-row13-rack2-host8-servo " if type \"logger\" > /dev/null 2>&1;
    then logger -tag \"autotest\" \"server[stack::repair|run|wrapper] ->
    ssh_run(/usr/share/vboot/bin/set_gbb_flags.sh 0)\";fi;
    /usr/share/vboot/bin/set_gbb_flags.sh 0"
Exit status: 1
Duration: 4.79011487961


Filed here for tracking purposes.
This has been seen before in another context: issue 727930
 
Blocking: 735121
Status: Assigned (was: Untriaged)
This is only for collecting all repair_failing modes.
Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be closed. Thank you.

Sign in to add a comment