ReleaseEngineering/Archive/Android Tegras: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 20: Line 20:


= Basic tegra management =
= Basic tegra management =
== Recover a foopy ==
If a foopy has been shutdown without having cleanly stopped all Tegras, you will need to do the following:
'''Note''': Establish the base screen session, if needed by trying screen -x first
ssh cltbld@foopy##
screen -x
cd /builds
./stop_cp.sh
./start_cp.sh
== Find what foopy a Tegra is on ==
== Find what foopy a Tegra is on ==
Open the Tegra Dashboard - the foopy number is shown to the right
Open the Tegra Dashboard - the foopy number is shown to the right


== Check status of Tegra(s) ==
== Check status of Tegra(s) ==
Find the Tegra on the Dashboard and then ssh to that foopy
Find the Tegra on the Dashboard and then ssh to that foopy


Line 52: Line 37:


== Clear an error flag ==
== Clear an error flag ==
Find the Tegra on the Dashboard, ssh to that foopy and then
Find the Tegra on the Dashboard, ssh to that foopy and then


Line 108: Line 92:
* reboot again - fairly common to have 2nd one clear it
* reboot again - fairly common to have 2nd one clear it
** especially if box responsive to ping & telnet (port 20701) after first reboot
** especially if box responsive to ping & telnet (port 20701) after first reboot
== Recover a foopy ==
If a foopy has been shutdown without having cleanly stopped all Tegras, you will need to do the following:
'''Note''': Establish the base screen session, if needed by trying screen -x first
ssh cltbld@foopy##
screen -x
cd /builds
./stop_cp.sh
./start_cp.sh


= Advanced tegra management =
= Advanced tegra management =
canmove, Confirmed users
2,850

edits

Navigation menu