A problem with afterburnt L4Linux

Yu MURATA <[email protected]>
Newsgroups gmane.comp.micro-kernel.l4.l4ka.general
Message-ID <[email protected]>
Hi,

I've tried to run afterburnt L4Linux on a real hardware.
First, I retrieved the afterburner project from current cvs.
Then, I compiled the project with the following command, 

$ make world

and I didn't get any errors.
However, when I tried to boot L4Linux, I got following
error messages.

=====================================================
KickStart 0.11.7
Detected multiboot compliant loader
 kernel     => 0x00156000
  (0x00813000,0x00016ff8)->0x00100000
  (0x0082a000,0x0000f440)->0x00118000
  (0x0083a000,0x0000b9e0)->0x00128000
  (0x00846000,0x00002edc)->0x00154000
 sigma0     => 0x00020000
  (0x00855000,0x00006044)->0x00020000
 roottask   => 0x00308880
  (0x0086c000,0x0000b93c)->0x00300000
  (0x00878000,0x000020dc)->0x0030c000
Launching kernel ...

L4Ka::Pistachio - built on May  8 2006 18:40:59 by root@505 using gcc version 3.4.4
hypervisor: Console initialized.
hypervisor: Finding memory ......................
hypervisor: Total memory: 0.348 GB | 356.703 MB | 365264 KB
hypervisor: Maximum useable byte address: 0x17f6ffff
hypervisor: Creating isolation domain, ID 0, at 0x00000000, size 0x00400000
hypervisor: Thread space, first TID: 0x000c8002 <32:2>, number of threads: 4096
hypervisor: Unknown CPU type, performance monitoring disabled.
hypervisor: Working set scanner TID: 0x000cc002 <33:2>
hypervisor: Try 0xbe000000 - 0xc0000000
hypervisor: size of dev remap table 32768
hypervisor: Device remap region: 0xbe000000, size 0x02000000
hypervisor: Virtual address space end: 0xbfffffff
hypervisor: Mapped bootloader module 0x00883000 - 0x008abfff
hypervisor: Mapped bootloader module 0x008ac000 - 0x00b3efff
hypervisor: Mapped bootinfo region 0x00001000 - 0x00001fff
hypervisor: Boot modules:
hypervisor: Module 0 at 0x00883000, size 0x00028d3f,
hypervisor:   command line: /afterburn/afterburn-wedge-l4ka-passthru vmstart vmsize=65536K wedgeinstall=16M wedgesize=16M
hypervisor: Module 1 at 0x008ac000, size 0x00292d54,
hypervisor:   command line: /afterburn/vmlinuz-2.6.9-driver root=/dev/hda2 ro console=tty console=ttyS0,115200
hypervisor: Loading module: /afterburn/afterburn-wedge-l4ka-passthru vmstart vmsize=65536K wedgeinstall=16M wedgesize=16M
hypervisor: Creating isolation domain, ID 1, at 0x00c00000, size 0x04000000
hypervisor: Thread space, first TID: 0x040c8002 <1032:2>, number of threads: 4096
hypervisor: Wedge virt offset 0xbc000000, phys offset 0x01000000, size 16777216
hypervisor: ELF entry virtual address: 0xbc000000
hypervisor:   Source 0x00884000, size 0x000147e5 --> hypervisor address 0x01c00000, VM address 0xbc000000
hypervisor:   Source 0x00899000, size 0x000095dc --> hypervisor address 0x01c16000, VM address 0xbc016000
hypervisor: Hypervisor shared page at VM address 0xbc01b000, size 0x00000518
hypervisor: Entry override, IP 0xbc000000, SP 0xbc01f52c
hypervisor: Installing module at VM phys address 0x03d6d000, size 0x00292d54
hypervisor: KIP at 0xbc019000, size 0x00001000
hypervisor: UTCB at 0xbc01a000, size 0x00001000
hypervisor: Main thread TID: 0x040c8002 <1032:2>
hypervisor: Entering the server loop ...
afterburn: Console initialized.
afterburn: irq thread's TID: 0xbc01a300
afterburn: main thread's TID: 0xbc01a500
afterburn: Entering monitor loop, TID 0x040c8002 <1032:2>
afterburn: Entering IRQ loop, TID 0x040cc002 <1033:2>
afterburn: Entering main VM thread, TID 0x040d0002 <1034:2>
afterburn: ELF entry virtual address: 0x80100000
afterburn:   Source 0x03d6e000, size 0x00283086 --> paddr 0x00100000, vaddr 0x80100000
afterburn: Total patchups: 5497
afterburn: Total device patchups: 20
afterburn: Total device patchups: 36
afterburn: Total device patchups: 33
afterburn: Total device patchups: 16
afterburn: Total device patchups: 1
afterburn: Total bitop patchups: 5
afterburn: Required exports to guest: 12
afterburn: Total exports accepted by guest: 13
afterburn: Required from guest: 2
afterburn: Total from guest: 2
afterburn: Starting the VM, ip 0x00100000, sp 0xbc0236b0
Linux version 2.6.9-afterburn-driver (root@505) (gcc version 3.4.4) #1 Mon May 8 19:38:26 JST 2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000a0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000001000000 (usable)
 BIOS-e820: 0000000001000000 - 0000000002000000 (reserved)
 BIOS-e820: 0000000002000000 - 0000000004000000 (usable)
64MB LOWMEM available.
DMI present.
Built 1 zonelists
Kernel co)
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 184k freed
afterburn: Unsupported exception from user-level, user ip 0x77edc2ac, TID 0x040d4001 <1035:1>
afterburn: VM panic.  Halting VM threads.
=====================================================


========= My environment ============================
OS: Debian Sarge (kernel 2.6.13.4)
gcc: 3.4.4
=====================================================


========= Grub Menu =================================
title = p3: Afterburnt Linux on Marzipan with Device Pass-Through
kernel = /afterburn/kickstart-serial
module = /afterburn/pistachio-p3
module = /afterburn/sigma0-serial
module = /afterburn/marzipan
module = /afterburn/afterburn-wedge-l4ka-passthru vmstart vmsize=65536K wedgeinstall=16M wedgesize=16M
module = /afterburn/vmlinuz-2.6.9-driver root=/dev/hda2 ro console=tty console=ttyS0,115200
=====================================================


Does anyone have any suggestions about this?  Any help would
be appreciated.


Thanks in advance,
Yu Murata

-- 
Yu Murata <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.