Closed Bug 718697 Opened 13 years ago Closed 13 years ago

tegras failing to recover after multiple power cycles

Categories

(Infrastructure & Operations :: RelOps: General, task)

ARM
Android
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: u429623, Assigned: dividehex)

Details

The follow tegra units have not recovered after numerous PDU power cycling events. They need some TLC: tegra-031 (agent check fail since 01-10-2012 15:29:53) tegra-042 (ping fail since 01-01-2012 12:43:24) tegra-083 (agent check fail since 01-11-2012 19:18:23) tegra-121 (agent check fail since 01-09-2012 17:08:30)
Assignee: server-ops-releng → jwatkins
colo-trip: --- → mtv1
tegra-268
2012-01-19 13:15:08 tegra-121 p online active active :: hung during boot. I could ping it but it wouldn't load the desktop. re-imaged and initialized. 2012-01-19 13:16:22 tegra-268 p online active active :: Power cycling it a couple times by pulling the pwr didn't seem to get it online, but pressing the reset button did. 2012-01-19 14:00:35 tegra-083 p online active OFFLINE :: buildbot.tac.sed; hung during boot. I could ping it but it wouldn't load the desktop. re-imaged and initialized. 2012-01-19 14:00:08 tegra-042 p online active active :: The ACOK switch had been moved to the batt position. I moved it back to norm.
2012-01-19 14:45:03 tegra-031 s online active OFFLINE :: This tegra was not showing up in the dashboard and had been removed from service. I brought this to bear and hwine 's attention. It was added back in to staging.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.