OK. Since Connect and the usual catch up, I've only just got round to looking 
at the health failures on production. Quite a few problems, with a common 
theme...

------------
origen07
------------
Network died. USB ethernet dongle was actually dead. Replaced it. Still doesn't 
work. We have Origens falling like flies at the moment!

------------
origen09
------------
http://validation.linaro.org/lava-server/scheduler/job/37461

Looks like the board hung while getting the test images. Rebooted and put back 
online.

------------
panda01
------------
http://validation.linaro.org/lava-server/scheduler/job/38038

Looks like control had a glitch and we kept getting "connection reset by peer" 
trying to wget. Back online.

------------
panda02
------------
http://validation.linaro.org/lava-server/scheduler/job/38039

Same as panda01. Put back online and it *still* failed in the same way. Will 
investigate.

------------
panda05
------------
http://validation.linaro.org/lava-server/scheduler/job/37905

This one would have been caught by the the "output returns to get prompt" 
and/or the "try three times" boot fixes

------------
panda06
------------
http://validation.linaro.org/lava-server/scheduler/job/37726

Same as panda05

------------
panda11
------------
http://validation.linaro.org/lava-server/scheduler/job/36722

Very odd. Looks like the test image, or the test partition, are corrupted. Went 
on to board and rebooted test image, same problem. Will re-test. If it fails 
will replace sd card.

------------
panda13
------------
http://validation.linaro.org/lava-server/scheduler/job/37019

Very similar to panda11, except that this was in the android image. Same action 
as panda11.

------------
panda17
------------
http://validation.linaro.org/lava-server/scheduler/job/37291

The clue here are these lines:
mountall: fsck / [1088] terminated with status 4
mountall: Filesystem has errors: /
Errors were found while checking the disk drive for /.
Press F to attempt to fix the errors, I to ignore, S to skip mounting, or M for 
manual recovery

We never hit the prompt because it needed to do an fsck. Looked on board and 
all ok now. Retest.

------------
panda21
------------
http://validation.linaro.org/lava-server/scheduler/job/37864

Similar to panda11 and 13. Same action taken.

------------
panda22
------------
http://validation.linaro.org/lava-server/scheduler/job/37294

Same as panda17

------------
panda23
------------
http://validation.linaro.org/lava-server/scheduler/job/37779

Same as panda05.

----------------
panda-es01
----------------
http://validation.linaro.org/lava-server/scheduler/job/37676

Similar to panda11, 13 and 21

----------------
snowball02
----------------
http://validation.linaro.org/lava-server/scheduler/job/37295

Looks like the android test image just hangs on boot. Went on board, launched 
it. Same thing. Retest.

----------------
snowball06
----------------
http://validation.linaro.org/lava-server/scheduler/job/36157

eth0 didn't come up in master image. Would have been fixed by the "reboot" fix.


_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation

Reply via email to