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

Issue 704765 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Rialto Lab Status

Project Member Reported by haoweiw@google.com, Mar 23 2017

Issue description

Here is the bug to track the status of current Rialto status in the lab. 

4 Rialto devices setup in  Atlantis at location chromeos2-row2-rack10-host{7..10}. However, we are currently hitting error of consistent detecting hardware write protection which is preventing the firmware update on those devices. 

Please add in any contact points if needed to resolve this problem. 


 
Cc: joth@chromium.org gedis@chromium.org englab-sys-cros@google.com
Rialto does not follow the standard deployment workflow as it depends on servod to be working first.

Run on beaglebone/workstation/host

start servod BOARD=veyron_rialto

Verification
Process started
ps aux | grep servod
                                                                          
* Result *
root       625  1.8  7.9  30952 19652 ttyO1    Ssl+ 00:30   0:14 /usr/bin/python2.7 /usr/lib/python-exec/python2.7/servod --host 0.0.0.0 --board veyron_rialto --port 9999

root       645  0.0  6.0  29760 14888 ttyO1    S+   00:31   0:00 /usr/bin/python2.7 /usr/lib/python-exec/python2.7/servod --host 0.0.0.0 --board veyron_rialto --port 9999

root       646  0.0  6.1  29772 15116 ttyO1    S+   00:31   0:00 /usr/bin/python2.7 /usr/lib/python-exec/python2.7/servod --host 0.0.0.0 --board veyron_rialto --port 9999

This file should exist as well
cat /var/lib/servod/config_9999

* Result *                                                                        
BOARD=veyron_rialto

We have removed write protect from those 4 Rialtos using:
# Beaglebone, if servod is not runing:	
sudo start servod BOARD=veyron_rialto

# On the beaglebone
dut-control fw_wp_state:force_off

# On the Rialto
flashrom --wp-disable
flashrom --wp-status

Haowei, please retry these devices.

We also added about 8 more Rialtos to the rack, please let me know when you've enabled their ssh and I'll remove write-protect on all of them as well.


A couple of the shelves at the bottom did not have white ethernet cables for the Rialto. If you could please add them at your convenience we can get these final ones online too.
For any future Rialto lab setup I've updated the steps in the doc:
https://docs.google.com/document/d/1_98n_pbE2blNAfWJmM2HWTqoeZtXXPKRVhN686wqlHE/edit# 


Now the issue is switching if we need to have the DUT out of DEV mode. 

Should they be in/out of dev mode? or it doesn't matter?\
dev mode, cause otherwise the test image won't work.

But it will cause autotest fail. 

AutoservVerifyDependencyError: The host is in dev mode
03/27 12:53:56.250 ERROR|         traceback:0013| Traceback (most recent call last):
03/27 12:53:56.250 ERROR|         traceback:0013|   File "/usr/local/autotest/server/autoserv", line 514, in run_autoserv
03/27 12:53:56.251 ERROR|         traceback:0013|     job.repair(job_labels)
03/27 12:53:56.251 ERROR|         traceback:0013|   File "/usr/local/autotest/server/server_job.py", line 517, in repair
03/27 12:53:56.252 ERROR|         traceback:0013|     self._execute_code(REPAIR_CONTROL_FILE, namespace, protect=False)
03/27 12:53:56.252 ERROR|         traceback:0013|   File "/usr/local/autotest/server/server_job.py", line 1301, in _execute_code
03/27 12:53:56.253 ERROR|         traceback:0013|     execfile(code_file, namespace, namespace)
03/27 12:53:56.253 ERROR|         traceback:0013|   File "/usr/local/autotest/server/control_segments/repair", line 47, in <module>
03/27 12:53:56.253 ERROR|         traceback:0013|     job.parallel_simple(repair, machines)
03/27 12:53:56.254 ERROR|         traceback:0013|   File "/usr/local/autotest/server/server_job.py", line 625, in parallel_simple
03/27 12:53:56.254 ERROR|         traceback:0013|     return_results=return_results)
03/27 12:53:56.255 ERROR|         traceback:0013|   File "/usr/local/autotest/server/subcommand.py", line 93, in parallel_simple
03/27 12:53:56.255 ERROR|         traceback:0013|     function(arg)
03/27 12:53:56.256 ERROR|         traceback:0013|   File "/usr/local/autotest/server/control_segments/repair", line 41, in repair
03/27 12:53:56.256 ERROR|         traceback:0013|     raise Exception('')
03/27 12:53:56.257 ERROR|         traceback:0013| Exception
03/27 12:53:56.713 ERROR|          autoserv:0765| 1
Traceback (most recent call last):
  File "/usr/local/autotest/server/autoserv", line 761, in main
    use_ssp)
  File "/usr/local/autotest/server/autoserv", line 574, in run_autoserv
    sys.exit(exit_code)
SystemExit: 1

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos2-row2-rack10-host8/60435371-repair
Deployed 12 Rialtos, 6 in BVT pool and 6 in suites pool

Comment 7 by aut...@google.com, Mar 30 2017

Owner: haoweiw@chromium.org
Status: Fixed (was: Untriaged)
Closing this ticket. Any relative issue please open a new bug. 

Comment 9 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61
Status: Verified (was: Fixed)
Closing. Please reopen it if its not fixed. Thanks!

Sign in to add a comment