Reloading L4Linux problem

[Adam Lackorzynski]

Hi,

On Mon Mar 13, 2006 at 16:18:14 +0900, Jugwan Eom wrote:
> Thanks martin for advice. I tried to reload L4Linux with event server
> but still failed though some incorrect behavior disappeared. After
> shutdown loaded L4Linux, l4con showed the memory used by L4Linux was
> returned. But using 'a' command in run (not l4con, it's my mistake in
> previous mail) memory region is still allocated to the L4Linux. And

That's probably because you didn't specify --events for the loader.

> reloading L4Linux still failed. Booting reloaded L4Linux hung in
> acquiring IRQ 11 (network card) and CPU utilization became 100%.

I'll try to investigate this.

> And I couldn't find using levent library or event related functions
> (levents_*) in either L4Linux Makefile (l4linux-2.6/arch/l4/Makefile) or
> any L4Linux sources. This is needed to use the event server, isn't it?

No, an application itself doesn't need to know of this service, just the
servers that allocate resources for a client.

> title Fiasco / l4linux
> root (hd0,0)
> kernel /fiasco/l4/v2/bootstrap
> modaddr 0x06000000
> module /fiasco/l4/v2/fiasco -nokdb -loadcnt -nowait -serial_esc -comspeed 115200
>  -comport 1
> module /fiasco/l4/v2/sigma0
> module /fiasco/l4/v2/roottask task modname "bmodfs" module module module module module module
> module /fiasco/l4/v2/names --events
> module /fiasco/l4/v2/log
> module /fiasco/l4/v2/dm_phys --isa=0x00800000 -v --events
> module /fiasco/l4/v2/simple_ts -t 380 --events
> module /fiasco/l4/v2/rtc --events
> module /fiasco/l4/v2/l4io --noirq --events
> module /fiasco/l4/v2/events
> module /fiasco/l4/v2/bmodfs --events
>  module /fiasco/l4/v2/libloader.s.so
>  module /l4/cfg/run.bmodfs.cfg
>  module /fiasco/l4/v2/run
>  module /fiasco/l4/lx/vmlinuz26
>  module /l4/cfg/lx/l4linux26_rd_tty.cfg
>  module /l4/rd/tty.rd
> module /fiasco/l4/v2/l4exec --events
> module /fiasco/l4/v2/con --l4io --cpuload --events
> module /fiasco/l4/v2/loader --fprov=BMODFS run.bmodfs.cfg l4linux26_rd_tty.cfg
> vbeset 0x117

My config looks similar to the following:

...
module .../events
module .../names --events
module .../log
module .../dm_phys --events
module .../simple_ts -t 400 --events 
module .../rtc
module .../l4io --noirq
module .../l4exec
module .../con --events --l4io --cpuload
module .../bmodfs
  modules ...
module .../loader --events apps...

That are all '--events' switches that need to appear.




Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/