problem booting L4Linux

Adam Lackorzynski adam at os.inf.tu-dresden.de
Mon Sep 24 23:13:22 CEST 2012


Hi,

On Thu Sep 20, 2012 at 13:04:35 +0200, Death Jester wrote:
> does anybody know what the following message means:
> -------------------------------------------------------------
> [0:59000;8ffff]
> [0:97000;97fff]
> [0:9f000;13ffff]
> [4:140000;174fff]
> [0:175000;177fff]
> [4:178000;18efff]
> [0:18f000;100efff]
> [4:100f000;100ffff]
> [0:1010000;10fffff]
> [4:1100000;1528fff]
> [0:1529000;effffff]
> IOMEM:----------------------
> [0:10000000;ffffffff]
> MOE: Hello world
> MOE: found 240780 KByte free memory
> MOE: found RAM from 59000 to f000000
> MOE: allocated 239 KByte for the page array @0x9f000
> MOE: virtual user address space [0-bfffffff]
> MOE: rom name space cap -> [C:501000]
>   BOOTFS: [14b4000-14cd448] [C:503000] l4re
>   BOOTFS: [14ce000-1528bc8] [C:504000] ned
>   BOOTFS: [1100000-1100189] [C:505000] l4lx.cfg
>   BOOTFS: [1101000-11eb1ac] [C:506000] io
>   BOOTFS: [11ec000-11ec0bd] [C:507000] arm-rv.io
>   BOOTFS: [11ed000-14ae474] [C:508000] vmlinuz.arm
>   BOOTFS: [14af000-14b3a86] [C:509000] ramdisk-arm.rd
> MOE: cmdline: moe rom/l4lx.cfg
> MOE: Starting: rom/ned rom/l4lx.cfg
> MOE: loading 'rom/ned'
> Ned says: Hi World!
> Ned: loading file: 'rom/l4lx.cfg'
> Ned: ERROR: cannot read rom/l4lx.cfg: Invalid argument
> ------------------------------------------------------------------
> 
> My 'l4lx.cfg' file is the default file from the l4/conf/examples
> folder. I haven't changed anything. And my 'modules.list' looks like
> this:
> --------------------------
> modaddr 0x01100000
> 
> entry L4Linux_ARM
> kernel fiasco -serial_esc
> roottask moe rom/l4lx.cfg
> module l4re
> module ned
> module l4lx.cfg
> module io
> module arm-rv.io
> module vmlinuz.arm
> module ramdisk-arm.rd
> ---------------------------
> 
> I'm using the latest L4re, Fiasco and L4Linux checked out from the SVN
> today and I'm running a Kirkwood based device.

Mysterious, looks like the lua interpreter is erroring out while reading
the file. Never seen this before with this error code. Does it also
happen when you use another target, such as QEmu's realview or similar?




Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/




More information about the l4-hackers mailing list