877710 - (tegra-114) tegra-114 problem tracking

Status: RESOLVED FIXED

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

Comment 1

[Justin Wood (:Callek)]

Tuesday, September 24, 2013 8:40:06 AM

Comment 2

[Salvador Espinoza [:sal]]

flashed and reimaged

Comment 3

[[e-mail] (:bhearsum)]

Back in production.

Comment 4

[[e-mail] (:bhearsum)]

2014-01-16 10:16:03 tegra-114 p    online   active  OFFLINE :: error.flg [Automation Error: Unable to connect to device after 5 attempts] 

pdu reboot didn't help

Comment 5

[Eric Ramirez [:Eric]]

SD card replaced & reimaged/flashed.

Comment 6

[Chris Cooper [:coop] (he/him)]

error.flg is set to:

Automation Error: Unable to connect to device after 5 attempts

Comment 7

[Van Le [:van]]

tegra reimaged and flashed.

[[e-mail]3 ~]$ telnet tegra-114.tegra.releng.scl3.mozilla.com 20701
Trying 10.26.85.89...
Connected to tegra-114.tegra.releng.scl3.mozilla.com.
Escape character is '^]'.
$>

Comment 8

[Justin Wood (:Callek)]

Taking jobs again

Comment 9

[John Hopkins (:jhopkins)]

Power cycled, waited a day.

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

SD card reformat failed:

$>exec newfs_msdos -F 32 /dev/block/vold/179:9
newfs_msdos: /dev/block/vold/179:9: No such file or directory
return code [1]

Comment 10

[John Hopkins (:jhopkins)]

Jobs are green so we'll just leave it be.

Comment 11

[Justin Wood (:Callek)]

foopy117 is going away, and these tegras are attached to it.

They are being decomissioned in Bug 1043938, and I just disabled all of them in slavealloc and marked them as decom with a comment pointing at Bug 1043938