l4linux starting - How can I see all Debug messages on serial line ?

"Rudolf Weber" <[email protected]>
Newsgroups gmane.comp.micro-kernel.l4.devel
Message-ID <trinity-e7497b0f-c6ae-4bb6-8039-17aefd2bd5b2-1374672364816@3capp-webde-bs30>
Gesendet: Donnerstag, 18. Juli 2013 um 23:58 Uhr
Von: "Adam Lackorzynski" <[email protected]>
An: "Rudolf Weber" <[email protected]>
Cc: "l4 l4hackerlist" <[email protected]>
Betreff: Re: l4linux: l4x_setup_memory:Cant get main memory
On Thu Jul 18, 2013 at 16:42:26 +0200, Rudolf Weber wrote:


>> The Booting-Result is better now, but an new error occurs:
>>
>> l4linux | Invalid IO-Port access at pc = 0080b476 port=0x110
>>
>> In the System.map I found
>> 0080b400 t el3_init_module
>> which is in the src/l4linux/drivers/net/ethernet/3com/3c509.c - Module.
>> Here the driver scans the io ports 0x110,0x120,...,0x200
>>
>> Ok - I will throw it out.
Yes, it boots further, loads the RAM-Disk and the booting in the mag-Window shows further errors.
I can't see the errors that quickly, and they don't appear in the log of qemu.

Question1: How can I see the error messages of L4linux on serial lines?

I tried this configuration without mag (and hope, all l4linux-Output should appear at the seril console)
modaddr  0x002000000

entry L4Linux
  kernel fiasco -serial_esc
  roottask fiasco -serial_esc
  roottask moe rom/l4linux.cfg
  module l4linux.cfg
  module l4re
  module ned
  module io
  module x86-legacy.devs
  module l4lx-x86.io
  module vmlinuz
  module ramdisk-x86.rd

and l4linux.cfg
loader = L4.default_loader;

-- io - server
vbus_l4linux = loader:new_channel();
vbus_input   = loader:new_channel();

loader:start(
  {
     caps = {
      sigma0  = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0);
      icu     = L4.Env.icu;
      input   = vbus_input:svr();
      l4linux = vbus_l4linux:svr();
     },
  },  "rom/io rom/x86-legacy.devs rom/l4lx-x86.io");

loader:start(
  {
     caps = {
        log = L4.Env.log:m("rws"),
        vbus = vbus_l4linux;
     },
     l4re_dbg = L4.Dbg.Warn,
     log = { "l4linux", "yellow" },
  }, "rom/vmlinuz mem=64M l4x_rd=rom/ramdisk-x86.rd root=1:0 ramdisk_size=4000 init=/bin/sh");

Result:
  I can't see any severe errors, but the prompt of the /bin/sh is not shown :-(

I opened the Fiasco - Debugger, looked the backtrace of vmlinux-thread and the question come:
Question2: How do I map the addresses to the System.map? -> Is there any tutorial available ?   


The l4linux configuration x86-ux_defconfig works with grub-Module-configuration
 modaddr 0x02000000

default-kernel fiasco -serial_esc
default-bootstrap bootstrap

entry L4Linux-mag-x86
roottask moe rom/l4lx-gfx.cfg
module l4re
module ned
module l4lx-gfx.cfg
module io
module fb-drv
module mag
module x86-legacy.devs
module l4lx-x86.io
module vmlinuz
module ramdisk-x86.rd


Related to Question1 is
Question3:How can I see the messages of l4linux on serialline ?

My try:
The configuration:
modaddr  0x002000000

entry L4Linux
  kernel fiasco -serial_esc
  roottask fiasco -serial_esc
  roottask moe rom/l4linux.cfg
  module l4linux.cfg
  module l4re
  module ned
  module io
  module x86-legacy.devs
  module l4lx-x86.io
  module vmlinuz
  module ramdisk-x86.rd
with x86-legacy.devs and l4lx-x86.io from l4re-snapshot-2013060718
and l4linux.cfg like above don't lead to the prompt of the /bin/sh
but I can't understand what is wrong.


_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
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.