from: https://bugzilla.mozilla.org/show_bug.cgi?id=902657#c15 Vinh wrote: Majority of the pandas are in the "ready" state for releng to proceed with testing. The below pandas are failing and will need further troubleshooting. If releng can close out the working pandas in the "block" list above, then it will help me narrow down exactly which pandas need investigation (similar to tegra bugs). Thanks! panda-0172 failed_pxe_booting vhua-Unable to read "preEnv.txt" from mmc 0:1 ** panda-0444 failed_pxe_booting vhua-23.533630] panic occurred, switching back to text console panda-0479 failed_pxe_booting vhua-not in chassis panda-0482 failed_pxe_booting vhua-not in chassis panda-0638 failed_pxe_booting panda-android-4.0.4_v3.1 panda-0797 failed_pxe_booting android panda-0081 failed_self_test dividehex-panda-intervention panda-0173 failed_self_test panda-0280 failed_self_test vhua-selftest.py[INFO]: test_preseed_file_integrity[FAILED] boot.scr : panda-0720 failed_self_test vhua-selftest.py[INFO]: test_mmc_blk_dev[FAILED] /dev/mmcblk0 - No such file or directory (tried multiple SD cards) panda-0678 locked_out android from: https://bugzilla.mozilla.org/show_bug.cgi?id=902657#c16 :dividehex wrote: (In reply to Vinh Hua [:vinh] from comment #15) > Majority of the pandas are in the "ready" state for releng to proceed with > testing. The below pandas are failing and will need further > troubleshooting. If releng can close out the working pandas in the "block" > list above, then it will help me narrow down exactly which pandas need > investigation (similar to tegra bugs). Thanks! > > > panda-0172 failed_pxe_booting vhua-Unable to read "preEnv.txt" from mmc 0:1 Unable to read "preEnv.txt" from mmc 0:1 is a normal error message. The uboot loader should continue to load/netboot Did you try swapping out the sdcard on this? if you did, does it halt at that msg or continue booting? > ** > panda-0444 failed_pxe_booting vhua-23.533630] panic occurred, switching > back to text console This sounds like a pandaboard hardware issue and it would be interesting to see a entire serial console capture to better identify the deeper issue here. It might be something we can add to selftest to check for. I would suggest swapping the sdcard if you haven't. If you have, and it still continues, remove the panda board (and order a replacement if we don't any spare boards) > panda-0479 failed_pxe_booting vhua-not in chassis > panda-0482 failed_pxe_booting vhua-not in chassis These 2 panda boards were removed from service and should be replaced. I'll remove them from mozpool. see bug836808 > panda-0638 failed_pxe_booting panda-android-4.0.4_v3.1 SDcard swap didn't work here? If so, we can assume the pandaboard is dead and should be replaced. > panda-0797 failed_pxe_booting android Same here? > panda-0081 failed_self_test dividehex-panda-intervention what is the reason the self_test failed here? (see device log) > panda-0173 failed_self_test Same. Why did it fail? (see device log) > panda-0280 failed_self_test vhua-selftest.py[INFO]: > test_preseed_file_integrity[FAILED] boot.scr : Boot.scr integrity check failure indicates outdated preseed image and should be fixed by: 1.) force state to 'troubleshooting' 2.) please_image -> repair-boot 3.) please_self_test > panda-0720 failed_self_test vhua-selftest.py[INFO]: > test_mmc_blk_dev[FAILED] /dev/mmcblk0 - No such file or directory (tried > multiple SD cards) This test indicates a bad pandaboard. Remove and replace. > panda-0678 locked_out android I have no idea why (or who) locked_out this panda. Check with #releng or #ateam. There should always be a bug # in the comment of the panda that is locked_out for obvious reasons. If no one claims they have reserved it, force state to troubleshooting and then run a selftest.

All pandas listed in bug has been remedied and noted in each individual bug. The following panda boards were not recoverable, indicating possibly bad board. Suggest decomm: panda-0172 panda-0720 panda-0444 panda-0638