778841 - (tegra-264) tegra-264 problem tracking

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Comment 1

[Justin Wood (:Callek)]

had to manually PDU cycle this, but its taking a job as of now.

Comment 2

[Justin Wood (:Callek)]

failed the last 5 jobs, with timeouts in verify rather than really catching the issue...

Comment 3

[[e-mail] (:bhearsum)]

Back in production.

Comment 4

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=15136599&tree=Mozilla-Inbound would be that same thing, timing out starting up verify

Comment 5

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=15141100&tree=Mozilla-Inbound

Comment 6

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=15139214&tree=Mozilla-Inbound

Comment 7

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=15137957&tree=Mozilla-Inbound

Comment 8

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=15144540&tree=Mozilla-Inbound

(8 reds and one kill on Try in a row, so this time I wasn't just panicking early.)

Comment 9

[Justin Wood (:Callek)]

IT handled this, stop and start_cp both run now

Comment 10

[Justin Wood (:Callek)]

No jobs taken on this device for >= 7 weeks

Comment 11

[Justin Wood (:Callek)]

(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

Comment 12

[Justin Wood (:Callek)]

had to cycle clientproxy to bring this back

Comment 13

[[e-mail] (:bhearsum)]

12 days, 3:51:23 since last job

Comment 14

[Ryan VanderMeulen [:RyanVM]]

Dying with random failures lately.
https://tbpl.mozilla.org/php/getParsedLog.php?id=23914144&tree=Mozilla-Inbound

Comment 15

[Armen [:armenzg]]

(In reply to Ryan VanderMeulen [:RyanVM] from comment #14)
> Dying with random failures lately.
> https://tbpl.mozilla.org/php/getParsedLog.php?id=23914144&tree=Mozilla-
> Inbound

disabled.cfg team

Comment 16

[Justin Wood (:Callek)]

Sending this slave to recovery
-->Automated message.

Comment 17

[Justin Wood (:Callek)]

Successfully recovered.

Comment 18

[Justin Wood (:Callek)]

Has an older-than-expected watcher ver, we're reimaging to get current.

Comment 19

[John Hopkins (:jhopkins)]

Power cycled, waited a day.

error.flg: Automation Error: Unable to connect to device after 5 attempts

SD card reformatted successfully:

$>exec newfs_msdos -F 32 /dev/block/vold/179:9
newfs_msdos: warning, /dev/block/vold/179:9 is not a character device
newfs_msdos: Skipping mount checks
/dev/block/vold/179:9: 15110464 sectors in 236101 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf0 spt=16 hds=4 hid=0 bsec=15114240 bspf=1845 rdcl=2 infs=1 bkbs=2
return code [0]
$>exec rebt
$>^]

Comment 20

[Jordan Lund (:jlund)]

looks like it ran until the 18th when:
'Remote Device Error: Unable to properly remove /mnt/sdcard/tests'

wiki says to reformat: https://wiki.mozilla.org/ReleaseEngineering/How_To/Android_Tegras#Unable_to_properly_remove_.2Fmnt.2Fsdcard.2Ftests


$>exec newfs_msdos -F 32 /dev/block/vold/179:9
newfs_msdos: warning, /dev/block/vold/179:9 is not a character device
newfs_msdos: Skipping mount checks
/dev/block/vold/179:9: 15110464 sectors in 236101 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf0 spt=16 hds=4 hid=0 bsec=15114240 bspf=1845 rdcl=2 infs=1 bkbs=2
return code [0]
$>exec rebt
$>^]
telnet> quit
Connection closed.

can be closed once jobs are being taken and greening

Comment 21

[Phil Ringnalda (:philor)]

Hasn't taken a job for 7 days.

Comment 22

[Phil Ringnalda (:philor)]

Disabled in slavealloc to stop the stream of pointless reboots.

Comment 23

[Van Le [:van]]

SD card replaced, tegra flashed and reimaged

vle@vle-10516 ~ $ telnet tegra-264.tegra.releng.scl3.mozilla.com 20701
Trying 10.26.85.212...
Connected to tegra-264.tegra.releng.scl3.mozilla.com.
Escape character is '^]'.
$>^]
telnet> q

Comment 24

[Phil Ringnalda (:philor)]

Reenabled.