Bug 786704 (tegra-328)

tegra-328 problem tracking

RESOLVED FIXED

Status

Release Engineering
Buildduty
RESOLVED FIXED
5 years ago
8 months ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildduty], URL)

(Reporter)

Description

5 years ago
Tegra agent check is failing, trying a PDU reboot.
(Reporter)

Comment 1

5 years ago
It's not even production actually -> don't care.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
It should be production, but this never actually had a successful job since we wired this -- we should reimage and swap its sdcard.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Updated

5 years ago
Depends on: 792692
swapped sdcard and tegra is pingable 


--- tegra-328.build.mtv1.mozilla.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 19.644/19.644/19.644/0.000 ms
(Reporter)

Comment 4

5 years ago
tried a pdu reboot, don't know what else to do.
Assignee: nobody → bugspam.Callek

Updated

5 years ago

Updated

5 years ago
Assignee: bugspam.Callek → nobody
Depends on: 822038
(Reporter)

Comment 5

5 years ago
pdu reboot
start_cp
(Reporter)

Comment 6

5 years ago
Still not working, back to recovery.
Depends on: 825335

Comment 7

5 years ago
reimaged, no card swap. last SD card swap was 9/21/12.
(mass change: filter on tegraCallek02reboot2013)

I just rebooted this device, hoping that many of the ones I'm doing tonight come back automatically. I'll check back in tomorrow to see if it did, if it does not I'll triage next step manually on a per-device basis.

---
Command I used (with a manual patch to the fabric script to allow this command)

(fabric)[jwood@dev-master01 fabric]$  python manage_foopies.py -j15 -f devices.json `for i in 021 032 036 039 046  048 061 064 066 067 071 074 079 081 082 083 084 088 093 104 106 108 115 116 118 129 152 154 164 168 169 174 179 182 184 187 189 200 207 217 223 228 234 248 255 264 270 277 285 290 294 295 297 298 300 302 304 305 306 307 308 309 310 311 312 314 315 316 319 320 321 322 323 324 325 326 328 329 330 331 332 333 335 336 337 338 339 340 341 342 343 345 346 347 348 349 350 354 355 356 358 359 360 361 362 363 364 365 367 368 369; do echo '-D' tegra-$i; done` reboot_tegra

The command does the reboot, one-at-a-time from the foopy the device is connected from. with one ssh connection per foopy

Updated

5 years ago
Depends on: 838687
Back from recovery
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → FIXED
Which lasted until March 26th.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 877722
tried to do one job since the reimage, but failed to come back up after installing the app.
Sending this slave to recovery
-->Automated message.
Depends on: 889567

Updated

5 years ago
Depends on: 892096

Updated

4 years ago
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
Blocks: 925447

Updated

4 years ago
No longer blocks: 925447
Depends on: 925447
Remote Device Error: unable to write to sdcard
Depends on: 934493
(Reporter)

Comment 14

4 years ago
Still not back in production, dunno what to do.
(Reporter)

Comment 15

4 years ago
I think it's back in production...
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → FIXED
abhorent RETRY amounts and purples, and very very few jobs even got around to
being attempted --> decomm
Depends on: 918168

Updated

4 years ago
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Updated

4 years ago
QA Contact: other → buildduty
(Reporter)

Comment 17

4 years ago
decommed
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.