provision failure: device does not reboot after 'crossystem clear_tpm_owner_request=1' |
||
Issue descriptionThis appears to be the failure on veyron_speedy-paladin: https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_speedy-paladin/builds/3332 I think clearing the TPM owner triggers a wipe of the stateful partition, which can take a long time. Maybe that's why it takes so long to come back up? I think this is also preventing the master-paladin from completing.
,
Oct 10 2016
The device log shows: 2016/10/10 09:40:59.265 DEBUG| cros_build_lib:0565| RunCommand: ssh -p 22 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInterval=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmpbRVzwr/testing_rsa root@chromeos4-row4-rack11-host7 -- 'crossystem clear_tpm_owner_request=1' Warning: Permanently added 'chromeos4-row4-rack11-host7,100.115.195.149' (RSA) to the list of known hosts. 2016/10/10 09:40:59.501 INFO | remote_access:0376| Rebooting chromeos4-row4-rack11-host7... 2016/10/10 09:40:59.501 DEBUG| cros_build_lib:0565| RunCommand: ssh -p 22 '-oConnectionAttempts=4' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=30' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInterval=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmpbRVzwr/testing_rsa root@chromeos4-row4-rack11-host7 -- 'touch /tmp/awaiting_reboot && reboot' 2016/10/10 09:41:04.762 DEBUG| cros_build_lib:0565| RunCommand: ssh -p 22 '-oConnectionAttempts=2' '-oUserKnownHostsFile=/dev/null' '-oProtocol=2' '-oConnectTimeout=2' '-oServerAliveCountMax=3' '-oStrictHostKeyChecking=no' '-oServerAliveInterval=10' '-oNumberOfPasswordPrompts=0' '-oIdentitiesOnly=yes' -i /tmp/ssh-tmpbRVzwr/testing_rsa root@chromeos4-row4-rack11-host7 -- "[ ! -e '/tmp/awaiting_reboot' ]" 2016/10/10 09:41:09.835 INFO | remote_access:0371| Cannot connect to device; reboot in progress. This continues until it times out and mosys eventlog on 100.115.195.149 shows: 121 | 2016-10-10 06:18:01 | System boot | 0 122 | 2016-10-10 06:26:36 | System boot | 0 123 | 2016-10-10 06:27:48 | System boot | 0 124 | 2016-10-10 08:51:24 | System boot | 0 125 | 2016-10-10 09:00:01 | System boot | 0 126 | 2016-10-10 09:14:22 | System boot | 0 127 | 2016-10-10 09:17:01 | System boot | 0 128 | 2016-10-10 09:20:23 | System boot | 0 129 | 2016-10-10 09:20:23 | Chrome OS Recovery Mode | Recovery Button Pressed 130 | 2016-10-10 09:27:56 | System boot | 0 131 | 2016-10-10 09:32:31 | System boot | 0 132 | 2016-10-10 09:41:08 | System boot | 0 133 | 2016-10-10 09:55:26 | System boot | 0 134 | 2016-10-10 09:58:04 | System boot | 0 135 | 2016-10-10 10:01:27 | System boot | 0 136 | 2016-10-10 10:01:27 | Chrome OS Recovery Mode | Recovery Button Pressed 137 | 2016-10-10 10:09:04 | System boot | 0 138 | 2016-10-10 10:13:40 | System boot | 0 139 | 2016-10-10 10:18:22 | System boot | 0 140 | 2016-10-10 10:18:43 | System boot | 0 141 | 2016-10-10 10:20:28 | System boot | 0 142 | 2016-10-10 13:15:54 | System boot | 0 143 | 2016-10-10 13:24:32 | System boot | 0 144 | 2016-10-10 13:25:38 | System boot | 0 145 | 2016-10-10 15:37:18 | System boot | 0 146 | 2016-10-10 15:45:37 | System boot | 0 147 | 2016-10-10 15:46:47 | System boot | 0 148 | 2016-10-10 15:53:28 | System boot | 0 I don't any recovery around the time of the reboot timeout so it's still a mystery why the dut didn't come back.
,
Apr 3 2018
archiving as this bug is over 1.5 years old. |
||
►
Sign in to add a comment |
||
Comment 1 by chirantan@chromium.org
, Oct 10 2016