Hi,
I'm running an edited and "old" (September 2012) version of L4Linux & uC-OS/II in top of Fiasco+L4RE (updated here). When launching the image I have generated, I have the following error:
MOE: cmdline: moe rom/l4lx_ucos.cfg MOE: Starting: rom/ned rom/l4lx_ucos.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx_ucos.cfg' Ucos | L4Re: FATAL: Exception Operation not permitted: '' Ucos | Exception: Operation not permitted: : backtrace ... l4linux | L4Re: FATAL: Exception Operation not permitted: '' l4linux | Exception: Operation not permitted: : backtrace ... io | Dev_factory: register factory for N2Hw6DeviceE io | GTF: register factory for 7Pci_dev io | GTF: register factory for N2Hw12Msi_resourceE io | Dev_factory: register factory for N2Hw11Gpio_deviceE io | Io service io | Ready. Waiting for request.
Can I see more about what's going wrong ? Can I see the backtrace those logs talks about ? :)
Hi,
On Wed May 29, 2013 at 11:07:11 +0200, Maximin Coste wrote:
I'm running an edited and "old" (September 2012) version of L4Linux & uC-OS/II in top of Fiasco+L4RE (updated here). When launching the image I have generated, I have the following error:
MOE: cmdline: moe rom/l4lx_ucos.cfg MOE: Starting: rom/ned rom/l4lx_ucos.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx_ucos.cfg' Ucos | L4Re: FATAL: Exception Operation not permitted: '' Ucos | Exception: Operation not permitted: : backtrace ... l4linux | L4Re: FATAL: Exception Operation not permitted: '' l4linux | Exception: Operation not permitted: : backtrace ... io | Dev_factory: register factory for N2Hw6DeviceE io | GTF: register factory for 7Pci_dev io | GTF: register factory for N2Hw12Msi_resourceE io | Dev_factory: register factory for N2Hw11Gpio_deviceE io | Io service io | Ready. Waiting for request.
Can I see more about what's going wrong ? Can I see the backtrace those logs talks about ? :)
Has the L4Linux been rebuilt against updated L4Re? Since there's no output at all from it it must be quite early, probably even before the Linux-internal loader runs that generates some output.
Adam
2013/5/31 Adam Lackorzynski adam@os.inf.tu-dresden.de:
Has the L4Linux been rebuilt against updated L4Re? Since there's no output at all from it it must be quite early, probably even before the Linux-internal loader runs that generates some output.
I figured out what's line on the l4x config file where failing:
mem = L4.Env.mem_alloc:create(L4.Proto.Factory, 10*1024*1024), -----^ it's 10 for uC/OS-II and 64 for L4Linux.
When those lines aren't commented I have the error from my previous mail.
Without those line, the L4Linux have a strange behavior: l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 0a400000 to 0a700000 [3072KiB] l4linux | panic: going to sleep forever, bye
Sudden kernel panic ?
On Fri May 31, 2013 at 12:28:15 +0200, Maximin Coste wrote:
2013/5/31 Adam Lackorzynski adam@os.inf.tu-dresden.de:
Has the L4Linux been rebuilt against updated L4Re? Since there's no output at all from it it must be quite early, probably even before the Linux-internal loader runs that generates some output.
I figured out what's line on the l4x config file where failing:
mem = L4.Env.mem_alloc:create(L4.Proto.Factory, 10*1024*1024),
Ah, make this: mem = L4.Env.mem_alloc:create(L4.Proto.Factory, 10*1024*1024):m("rws")
When those lines aren't commented I have the error from my previous mail.
Without those line, the L4Linux have a strange behavior: l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 0a400000 to 0a700000 [3072KiB] l4linux | panic: going to sleep forever, bye
Sudden kernel panic ?
The text is there but Linux's output subsystem is not yet up, so not displayed. Adding earlyprintk=1 should hopefully show more (needs to be compiled in).
Adam
l4-hackers@os.inf.tu-dresden.de