panic in L4Linux booting process

Adam Lackorzynski adam at
Tue Jul 4 12:18:17 CEST 2006

On Tue Jul 04, 2006 at 12:18:41 +0800, chenggh wrote:
>   #2  00660b4f : mount_block_root + 0x8f
>       /home/chenggh/test/l4linux-2.6/init/do_mounts.c:312
>   #3  00660d87 : mount_root + 0x87
>       /home/chenggh/test/l4linux-2.6/init/do_mounts.c:386

Now I see it, the Linux is not configured at all and thus does not know
which root filesystem to mount and panics.
I.e. you cannot only write:

  module (hd0,1)/boot/fiasco_L4/bmodfs --events
    module (hd0,1)/boot/fiasco_L4/vmlinuz26
    module (hd0,1)/boot/fiasco_L4/
  module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26

because that only loads the bare vmlinuz26 file without any
kernel command line configuration. Depending on what you want to do
(e.g. use a ramdisk or boot from disk) your configuration should more
look like:

  module (hd0,1)/boot/fiasco_L4/bmodfs --events
    module (hd0,1)/boot/fiasco_L4/vmlinuz26
    module (hd0,1)/boot/fiasco_L4/linux26.cfg
    module (hd0,1)/boot/fiasco_L4/
    module (hd0,1)/boot/fiasco_L4/ramdisk.rd
  module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS linux26.cfg

The linux26.cfg file should look like:

modpath "(hd0,1)/boot/fiasco_L4"
task "vmlinuz26" "earlyprintk=yes mem=64M root=1:0 load_ramdisk=1 ramdisk_size=2100 l4env_rd=ramdisk.rd" 

If you want to boot from disk, something like this could work:

modpath "(hd0,1)/boot/fiasco_L4"
task "vmlinuz26" "earlyprintk=yes mem=64M root=/dev/hda1" 
Then you do not need to load the ramdisk, of course.

Adam                 adam at

More information about the l4-hackers mailing list