Closed Bug 755736 Opened 13 years ago Closed 13 years ago

tegra recovery

Categories

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

Product:
Infrastructure & Operations
Component:
RelOps: General
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bear, Assigned: dividehex)

References

Details

(Whiteboard: [buildduty][buildslave][tegra])

No description provided.
See Also: → 754391
Blocks: tegra-204
Jake - for tegra-204, can you also confirm it's PDU assignment? inventory says pdu5.df202-1.build.mtv1.mozilla.com pduid: .AA5 but the tegra isn't being cycled via pdu. thanks
Assignee: server-ops-releng → mlarrain
colo-trip: --- → mtv1
Assignee: mlarrain → jwatkins
bear: I manually cycled the power via the pdu web interface and confirmed tegra-204 is correctly associated with pdu5.df202-1.build.mtv1.mozilla.com pduid: .AA5 The reboot got it to a point where I could ping it but just for safe measure I flashed the nvram and formatted/reinitialized the sdcard.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Alias: tegra-recovery
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.