hello together,
If I try to run the L4Linux or the hello example via a patched QEMU (with trustzone support) I get the following error message:
------------ ./qemu-system-arm -M vexpress-a9 -kernel /home/beresford/Work-Repositories/sepia/desastro/l4/build/images/bootstrap_hello.elf -initrd /home/beresford/Downloads/ramdisk-arm.rd -append "console=ttyAMA0 console=tty0 dhcp=on" -m 1024 -s -gdb tcp::5022
erster teilerfolg: Fiasco + L4 hüpfen zumindest mal an... ./qemu-system-arm -M vexpress-a9 -kernel /home/beresford/Work-Repositories/sepia/desastro/l4/build/images/bootstrap_L4linux_ARM.elf -initrd /home/beresford/Downloads/ramdisk-arm.rd -append "console=ttyAMA0 console=tty0 dhcp=off" -m 512 -smp 1 -gdb tcp::1234 -serial stdio bp147: attached 100e6000..100e6fff to TZDECPROT0[6] bp147: attached 100e4000..100e4fff to TZDECPROT0[4]
L4 Bootstrapper Build: #3 Tue Apr 19 09:46:31 CEST 2011, 4.5.1 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 10000000) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod09: 01500000-01800000: ramdisk-arm.rd mod08: 0124e000-014ff488: vmlinuz.arm mod07: 0124d000-0124d0bd: arm-rv.io mod06: 01162000-0124c7d4: io mod05: 01161000-01161189: l4lx.cfg mod04: 01105000-011601ac: ned mod03: 010e3000-01104488: l4re mod02: 010a5000-010e266c: moe mod01: 01093000-010a4304: sigma0 mod00: 01015000-01092a2c: fiasco Moving 10 modules to 1100000 with offset eb000 moving module 10 { 1500000-1800000 } -> { 15eb000-18eb000 } moving module 09 { 124e000-14ff488 } -> { 1339000-15ea488 } moving module 08 { 124d000-124d0bd } -> { 1338000-13380bd } moving module 07 { 1162000-124c7d4 } -> { 124d000-13377d4 } moving module 06 { 1161000-1161189 } -> { 124c000-124c189 } moving module 05 { 1105000-11601ac } -> { 11f0000-124b1ac } moving module 04 { 10e3000-1104488 } -> { 11ce000-11ef488 } moving module 03 { 10a5000-10e266c } -> { 1190000-11cd66c } moving module 02 { 1093000-10a4304 } -> { 117e000-118f304 } moving module 01 { 1015000-1092a2c } -> { 1100000-117da2c } Scanning fiasco Scanning sigma0 Scanning moe rom/l4lx.cfg Relocated mbi to [0x100f000-0x100f151] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list regions [ 1000, 19ff] { a00} Kern fiasco [ 2000, 8cfff] { 8b000} Kern fiasco [ 90000, 9e193] { e194} Sigma0 sigma0 [ 140000, 18b48b] { 4b48c} Root moe [ 1000000, 10143eb] { 143ec} Boot bootstrap [ 100f000, 100f24e] { 24f} Root Multiboot info [ 11ce000, 18eafff] { 71d000} Root Modules Memory API Version: (87) experimental Sigma0 config ip:00090000 sp:01013044 Roottask config ip:00140088 sp:00000000 Starting kernel fiasco at 00001000 Realview System ID: Rev=1 HBI=190 Build=f Arch=5 FPGA=00 L2: ID=00000000 Type=00000000 L2 cache enabled Hello from Startup::stage2
Assertion failed: 'prev_next' [ret=0xf000e9c8]
/home/beresford/Work-Repositories/sepia/desastro/kernel/fiasco/src/kern/buddy_alloc.cpp:23 at f000e834 ---------------------------------
If I remove the assertion check it executes a little bit more and I get the following error: --------------------------------- ... Starting kernel fiasco at 00001000 Realview System ID: Rev=1 HBI=190 Build=f Arch=5 FPGA=00 L2: ID=00000000 Type=00000000 L2 cache enabled Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf007a628-0xf007b030) Initialize page table Number of IRQs available at this GIC: 32 Number of IRQs available at this GIC: 32 Vmem_alloc::init() Cache config: ON ID_PFR0: 00001031 ID_PFR1: 00000011 ID_DFR0: 00000000 ID_AFR0: 00000000 ID_MMFR0: 00100103 ID_MMFR1: 20000000 ID_MMFR2: 01230000 ID_MMFR3: 00002111 Panic: UTCB pointer page allocation failure Press any key to reboot. ----------------------------------
Through the mailing list i found your posting from Thu, 25 Sep 2008 10:57:29 where you have suggested to check the
RAM_SIZE_MB in the l4 config file. I've checked it and it is set to 256MB as my qemu is set as well. I tried it further with 512MB and 1GB but it changes nothing.
Do you have any further ideas ?
kind regards, siegfried
Hi,
On Tue Apr 19, 2011 at 13:00:46 +0200, Siegfried Podesser wrote:
If I try to run the L4Linux or the hello example via a patched QEMU (with trustzone support) I get the following error message:
Which one?
./qemu-system-arm -M vexpress-a9 -kernel /home/beresford/Work-Repositories/sepia/desastro/l4/build/images/bootstrap_hello.elf -initrd /home/beresford/Downloads/ramdisk-arm.rd -append "console=ttyAMA0 console=tty0 dhcp=on" -m 1024 -s -gdb tcp::5022
erster teilerfolg: Fiasco + L4 hüpfen zumindest mal an... ./qemu-system-arm -M vexpress-a9 -kernel
Hmm, realview-pbx (as in the subject) or vexpress-a9? I'm not yet supporting vexpress-a9, and there are some differences. You adapted the board-ID?
Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 10000000) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB
Assertion failed: 'prev_next' [ret=0xf000e9c8]
/home/beresford/Work-Repositories/sepia/desastro/kernel/fiasco/src/kern/buddy_alloc.cpp:23 at f000e834
This is usually due to incorrect memory setups. vexpress-a9 has only 64MB starting at 0, the rest is at 0x60000000. And since it is given 256MB here this does not work.
If I remove the assertion check it executes a little bit more and I get the following error:
Good assertion then.
Through the mailing list i found your posting from Thu, 25 Sep 2008 10:57:29 where you have suggested to check the
RAM_SIZE_MB in the l4 config file. I've checked it and it is set to 256MB as my qemu is set as well. I tried it further with 512MB and 1GB but it changes nothing.
Do you have any further ideas ?
Use the realview-pbx model.
Adam
l4-hackers@os.inf.tu-dresden.de