problems running l4linux No.2

Adam Lackorzynski adam at
Thu Aug 6 23:48:25 CEST 2009


On Wed Aug 05, 2009 at 19:39:00 +0200, Stefan Kögel wrote:
> I started from a default l4linux26 kernel config. I did not touch
> anything, except for the things I had to, like acpi, apic, MTRR, MCE ..
> and the stuff that is missing (olpc, scx200 and these things).
> Everything else is default.
> The problem still exists but I was able to gather some info.
> Executing the l4linux26.cfg prints out:
> l4lx    | l4env_phys_to_virt: Could not translate phys. address 0x80000
> l4lx    | l4env_phys_to_virt: Could not translate phys. address 0x80010
> l4lx    | l4env_phys_to_virt: Could not translate phys. address 0x80020
> ...
> and continues untiel physical address 0x9fff0 and ends with a lock up of
> the computer.

L4Linux will not work but the system would still run.

My guess is that ISCSI_IBFT_FIND is enabled. This option causes scans
through physical memory, and the conversion functions in L4Linux are
built in a conservative way because if something goes wrong this can
lead to very subtle issues.
If my guess is wrong you should get a backtrace when you enable
earlyprintk on the kernel command line (i.e. it's already there but not
printed (yet)).

> I am wondering about these lines:
> ROOT: Task #0c is not allowed to execute cli/sti
> loader  | vmlinuz,#11: WARNING: Can't map I/O space, ROOT denies page
> (result=0
> loader  : 0004000)
> loader  | vmlinuz,#11: Not allowed to perform any I/O
> Could that be causing the error? How can I fix this?

Adding allow_cli as an option flag to the loader script will give
L4Linux all I/O rights and make the message go away.

Adam                 adam at

More information about the l4-hackers mailing list