pandaboard doesn't boot in LAVA with mainline kernel

Bug #1207348 reported by Milosz Wasilewski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LAVA Dispatcher
Fix Released
High
Tyler Baker

Bug Description

Build 116 (and a few previous ones) failed to boot in LAVA:
http://validation.linaro.org/dashboard/streams/private/team/linaro/ci-linux/bundles/1974c748cb8e14f27ecaf3419bc39e31f4073a09/

Last successful boot was with build 86:
http://validation.linaro.org/dashboard/streams/private/team/linaro/ci-linux/bundles/8e0eb21f288e0a0e1c1386163b5791ec41655916/

Both hwpacks boot fine on standalone board (without master image). using the same rootfs

Log messages from successful boot:
Panda # mmc part 0

Partition Map for MMC device 0 -- Partition Type: DOS

Partition Start Sector Num Sectors Type
    1 8192 106496 c
    2 114688 1982464 83
    3 2097152 131072 c
    4 2228224 28888064 5 Extd
    5 2230272 16777216 83
    6 19009536 4194304 83
    7 23205888 7910400 c
Panda # setenv bootcmd 'fatload mmc 0:3 0x80200000 uImage; fatload mmc 0:3 0x81600000 uInitrd; bootm 0x80200000 0x81600000'
Panda # setenv bootargs ' console=tty0 console=ttyO2,115200n8 root=LABEL=testrootfs rootwait ro earlyprintk fixrtc nocompcache vram=48M omapfb.vram=0:24M mem=456M@0x80000000 mem=512M@0xA0000000'
Panda # boot
reading uImage

4018048 bytes read
reading uInitrd

1575499 bytes read
## Booting kernel from Legacy Image at 80200000 ...
   Image Name: Linux
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 4017984 Bytes = 3.8 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81600000 ...
   Image Name: initramfs
   Image Type: ARM Linux RAMDisk Image (uncompressed)
   Data Size: 1575435 Bytes = 1.5 MiB
   Load Address: 00000000
   Entry Point: 00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0

Log messages from unsuccessful boot:
Panda # mmc part 0

Partition Map for MMC device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
  1 8192 106496 00000000-01 0c Boot
  2 114688 1982464 00000000-02 83
  3 2097152 131072 00000000-03 0c
  4 2228224 28888064 00000000-04 05 Extd
  5 2230272 8388608 00000000-05 83
  6 10620928 4194304 00000000-06 83
  7 14817280 16299008 00000000-07 0c
Panda # setenv bootcmd 'fatload mmc 0:3 0x80200000 uImage; fatload mmc 0:3 0x81600000 uInitrd; bootm 0x80200000 0x81600000'
Panda # setenv bootargs ' console=tty0 console=ttyO2,115200n8 root=LABEL=testrootfs rootwait ro earlyprintk fixrtc nocompcache vram=48M omapfb.vram=0:24M mem=456M@0x80000000 mem=512M@0xA0000000'
Panda # boot
reading uImage
4091376 bytes read
reading uInitrd
1575673 bytes read
## Booting kernel from Legacy Image at 80200000 ...
   Image Name: Linux
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 4091312 Bytes = 3.9 MiB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81600000 ...
   Image Name: initramfs
   Image Type: ARM Linux RAMDisk Image (uncompressed)
   Data Size: 1575609 Bytes = 1.5 MiB
   Load Address: 00000000
   Entry Point: 00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Related branches

Changed in lava-dispatcher:
assignee: nobody → Tyler Baker (tyler-baker)
status: New → Triaged
importance: Undecided → High
Revision history for this message
Tyler Baker (tyler-baker) wrote :

LAVA is not reading the boot cmds given in the image causing the improper boot arguements to be passed to the kernel.

Using the LAVA master image from here:

http://images.validation.linaro.org/lava-masters/panda-master.img.tgz

and the LAVA dispatcher branch from here:

https://code.launchpad.net/~tyler-baker/lava-dispatcher/bootloader-next

The result is that the mainline kernel boots on Panda:

http://community.validation.linaro.org/scheduler/job/178/log_file

Changed in lava-dispatcher:
status: Triaged → Fix Committed
Changed in lava-dispatcher:
milestone: none → 2013.08
Changed in lava-dispatcher:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.