Confirmed users
3,990
edits
ReleaseEngineering/Archive/Android Tegras: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Archive/Android Tegras (view source)
Revision as of 17:01, 17 February 2012
, 17 February 2012→power cycle a Tegra
| Line 68: | Line 68: | ||
== power cycle a Tegra == | == power cycle a Tegra == | ||
Find the Tegra on the Dashboard and then ssh to that foopy | Find the Tegra on the Dashboard and then ssh to that foopy | ||
ssh cltbld@foopy## | ssh cltbld@foopy## | ||
/builds/check.sh -t tegra-## -c | /builds/check.sh -t tegra-## -c | ||
| Line 76: | Line 74: | ||
You have to wait approximately 5 minutes before you can check the status of the slave. | You have to wait approximately 5 minutes before you can check the status of the slave. | ||
What "check.py -c" does is to check that a tegra is really offline and then reboot through the PDU. | |||
"Reboot a Tegra through the PDU" is doing a hardcore reboot without checking that the tegra is really down. | |||
This means that if this section does not recover you will need to file a bug for ServerOps::Releng to get to it. | |||
<strike> | |||
If the above did not work, then you will need to [[#Reboot a Tegra through the PDU]]. | If the above did not work, then you will need to [[#Reboot a Tegra through the PDU]]. | ||
</strike> | |||
== clear an error flag == | == clear an error flag == | ||