Make sure host is locked in cautotest before swapping.

Also forgot - this is a conductive setup, so please ensure:
  Confirm write-protect is disabled (flashrom -p host --wp-status; flashrom -p ec --wp-status; flashrom -p ec:dev=1 --wp-status (only for Type-C devices))
  Check for servo debug header
  Install servo cable
  Install pigtails
  Verify no firmware screen on boot
  Install factory firmware (chromeos-firmwareupdate --mode=factory)
  Boot test image in dev mode (3 finger, insert USB w/ test image)
  Run chromeos-tpm-recovery to clear TPM; reboot
  Switch to normal mode (/usr/share/vboot/bin/setgbbflags.sh 0)
  Run network_WiFi_VerifyRouter on test-station
  Connect servo and run platform_InstallTestImage on test-station
  Run network_WiFi_VerifyRouter in B1758
  Run platform_InstallTestImage in B1758

Reloaded the build from USB stick from servo on android1758-row4-rack8-host2.
The unit seems to be working and able to ping the host.
Pressed the "Reverify" button from the autotest and will monitor the unit for few days. Able to ping the host.

Verify device (asset tag: C070011) powers on and boots Done
Switch to dev mode Done
Install ToT test image Done
Confirm write-protect is disabled (flashrom -p host --wp-status; flashrom -p ec --wp-status; flashrom -p ec:dev=1 --wp-status Done
Verify no firmware screen on boot Done
Install factory firmware (chromeos-firmwareupdate --mode=factory) Done
Boot test image in dev mode (3 finger, insert USB w/ test image) Done
Run chromeos-tpm-recovery to clear TPM; reboot Done
Switch to normal mode (/usr/share/vboot/bin/setgbbflags.sh 0) Done

-------------------------------------------------------------------------------------------------------
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter                           [  PASSED  ]
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter [  PASSED  ]
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_149                                                               -49
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_1_ch_6                                                                 -63
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_149                                                               -75
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_2_ch_6                                                                 -51
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_149                                                               -54
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6                                                                 -57
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6{1}                                                              -54
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_0_bm_3_ch_6{2}                                                              -55
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_149                                                               -49
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_1_ch_6                                                                 -65
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_149                                                               -74
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_2_ch_6                                                                 -52
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_149                                                               -55
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_6                                                                 -55
/tmp/test_that_results_FX0cOA/results-1-network_WiFi_VerifyRouter/network_WiFi_VerifyRouter   signal_for_ap_1_bm_3_ch_6{1}                                                              -55
-------------------------------------------------------------------------------------------------------
Total PASS: 2/2 (100%)

Device status for android1758-row4-rack8-host2 shows up as "repair failed". Everything looks pingable. Can you check this Paul?

Replaced the Reks and under repairing mode.

Run platform_InstallTestImage Done

:54:50 INFO | autoserv| Setting power_state to off
08:55:05 INFO | autoserv| Setting prtctl4_pwren to off
08:55:07 INFO | autoserv| Setting power_state to on
08:55:09 INFO | autoserv| Waiting for DUT to come back up.
08:56:33 INFO | autoserv| [stderr] mux_client_request_session: read from master failed: Broken pipe
08:56:33 INFO | autoserv| [stderr] Warning: Permanently added 'chromeos1-test-station.cros,172.27.214.175' (RSA) to the list of known hosts.
08:56:33 INFO | autoserv| GOOD	platform_InstallTestImage	platform_InstallTestImage	timestamp=1472392593	localtime=Aug 28 08:56:33	completed successfully
08:56:33 INFO | autoserv| END GOOD	platform_InstallTestImage	platform_InstallTestImage	timestamp=1472392593	localtime=Aug 28 08:56:33
08:56:33 INFO | autoserv| Finished processing control file
08:56:33 INFO | autoserv| Starting master ssh connection '/usr/bin/ssh -a -x -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_7kanKxssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/tmp/tmpGRzPaz -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=300 -l root -p 22 chromeos1-test-station.cros'
08:56:34 INFO | autoserv| Starting master ssh connection '/usr/bin/ssh -a -x   -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_lo_yVfssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos1-test-station.cros'
08:56:35 INFO | autoserv| There are no orphaned crashes; deleting /tmp/test_that_results_qJ_ZW3/results-1-platform_InstallTestImage/crashinfo.chromeos1-test-station.cros
08:56:35 INFO | autoserv| Starting master ssh connection '/usr/bin/ssh -a -x -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_jr3q8gssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/tmp/tmpYC4Ve1 -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=300 -l root -p 22 chromeos1-test-station.cros'
08:56:36 INFO | autoserv| Starting master ssh connection '/usr/bin/ssh -a -x   -N -o ControlMaster=yes -o ControlPath=/tmp/_autotmp_xGqIyzssh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 22 chromeos1-test-station.cros'
08:56:36 INFO | autoserv| get_network_stats: at-end RXbytes 278718 TXbytes 40026
08:56:41 INFO | autoserv| record_state_duration failed: job_or_task_id=None, hostname=chromeos1-test-station.cros, status=Running
-------------------------------------------------------------------------------------------------------
/tmp/test_that_results_qJ_ZW3/results-1-platform_InstallTestImage                           [  PASSED  ]
/tmp/test_that_results_qJ_ZW3/results-1-platform_InstallTestImage/platform_InstallTestImage [  PASSED  ]
-------------------------------------------------------------------------------------------------------
Total PASS: 2/2 (100%)

This may be a rig problem. We can try to move this to a cell upstairs, a couple of components at a time.

Steps:
  1. Lock rack8-host2
  2. Move DUT & router/pcap setup (including Ethernet dongles) to a wificell upstairs
  3. Verify can still ping hostnames
  4. Unlock in cautotest, let tests run overnight
  5. Check device status in the morning (Repair Failed? black screen?)
  6. If device is fine, move servo and repeat Steps 3-5. If setup with servo is fine, move chameleon and repeat Steps 3-5.

1. Lock rack8-host2 Done
2. Move DUT & router/pcap setup (including Ethernet dongles) to a wificell upstairs Done
3. Verify can still ping hostnames Done
4. Unlock in cautotest, let tests run overnight Done

Check device status in the morning (Repair Failed? black screen?)
The autotest shows "Repair Failed" and also it's blank screen.
It's the same problem after moving the testbed to upstaires.
The system can be back by esc-refresh-power and then boot from USB and then reboot from sv2 and then the system goes back to normal mode.
There might be an issue with Reks and might need to file the bug.

Reassigning to dschimmels@ to pass onto donator@. After these bugs are completed, we can file bugs with Buganizer and assign directly to donator@.

You started fixing this bug over two years ago. Are you still working on it? You can update the status to "archived", "wontfix", or "closed". You can remove yourself as owner and change status to "untriaged", but if this is still a real bug, please do not sit on it.