Using run with bmodfs as file-provider

[Stefan Kalkowski]

Hi,

i have a problem with using 'run' and bmodfs as file-provider. When i
used tftp everything went fine. But now i have to use bmodfs, because i
also need flips and that clashs with tftp. So i gave 'run' the argument
'--fprov=BMODFS'. But after a short while it exits:

run     | our_exit(): Exiting with rc=-2
run     | Return reboots, "s" sleeps, "e" kills task, "k" enters L4 kdbg

full debugger output can you find here:
http://www.inf.tu-dresden.de/~sk852421/fiasco/run.out

Here is my menu.lst entry:

title=L4Linux-2.6 with DOpE
root (nd)
kernel /drops/l4/bin/x86_586/l4v2/rmgr -sigma0 task modname "L4Linux
task" task modname "l4dope" boot_priority 0xB2 task modname "l4io"
boot_priority 0xc0 task modname "bmodfs" module module module module
modaddr 0x02000000
vbeset 0x114
module /drops/l4/kernel/fiasco/build/main -nowait -nokdb -serial_esc
-comspeed 115200 -comport 1
module /drops/l4/bin/x86_586/l4v2/sigma0
module /drops/l4/bin/x86_586/l4v2/names --events
module /drops/l4/bin/x86_586/l4v2/log
module /drops/l4/bin/x86_586/l4v2/events
module /drops/l4/bin/x86_586/l4v2/dm_phys --events
module /drops/l4/bin/x86_586/l4v2/simple_ts --events
module /drops/l4/bin/x86_586/l4v2/rtc
module /drops/l4/bin/x86_586/l4v2/bmodfs
module /drops/l4/bin/x86_586/l4v2/run
module /drops/l4/bin/x86_586/l4v2/libloader.s.so
module /drops/l4linux-2.6/vmlinuz26
module /drops/scripts/l4linux26-dope
module /drops/l4/bin/x86_586/l4v2/l4exec
module /drops/l4/bin/x86_586/l4v2/l4dope --l4io --events
module /drops/l4/bin/x86_586/l4v2/proxygon
module /drops/l4/bin/x86_586/l4v2/l4io --noirq
module /drops/l4/bin/x86_586/l4v2/name_server
module /drops/l4/bin/x86_586/l4v2/flips-lxdrv
module /drops/l4/bin/x86_586/l4v2/mini_ifconfig eth0 192.168.0.2
255.255.255.0 192.168.0.3
module /drops/l4/bin/x86_586/l4v2/webproxy
module /drops/l4/bin/x86_586/l4v2/loader --events --fprov=BMODFS run
--fprov=BMODFS l4linux26-dope

so is it at present possible to use run in combination with bmodfs? For
me it looks like that it should be possible.

a backtrace of that thread:

(c.02) jdb: bt thread=c.02

backtrace (thread c.02, fp=00afff6c, pc=01306ef1):

  #1  01306ef1 : our_exit + 0x81

      /drops/l4/pkg/oskit10_support_l4env/lib/src/exit.c:56

  #2  01307bd7 : _exit + 0x17

  #3  01307406 : exit + 0x16

  #4  00013a17 : __startup_main + 0x37

      /drops/l4/pkg/loader/lib/runtime/main.c:83

  #5  00015c23 : l4th_thread_start + 0x73

      /drops/l4/pkg/thread/lib/src/create.c:72

  #6  00018e28 : l4th_thread_entry + 0x18

      /drops/l4/pkg/thread/lib/src/l4.c:113


 --kernel-bt-follows-- (don't trust w/o frame pointer!!)

  #1  f0005a70

  #2  f0004d8e

  #3  f000a7b6

  #4  f00054fe

  #5  f0016aad

  #6  f0006572

  #7  f00051a2

  #8  f0005c1d

  #9  f0005a5c

 #10  f0006335

 #11  f0007443

 #12  f002683c


thank you in advance
Stefan

-- 
Stefan Kalkowski

GNU PGP-Key:
https://www.inf.tu-dresden.de/~sk852421