Hi Hackers,
yesterday I was running Dope with L4Linux. Inside the L4Linux-framebuffer I was compiling some applications, which produce lots of output in a very short time. Well, exactly at that point DoPe crashed. Connecting via my serial port to the kdb I got "Dope exited with -1" or something like that. I will try to reproduce that error or is this known already?
Best regards,
Marcel Selhorst
Hi Marcel,
yesterday I was running Dope with L4Linux. Inside the L4Linux-framebuffer I was compiling some applications, which produce lots of output in a very short time. Well, exactly at that point DoPe crashed. Connecting via my serial port to the kdb I got "Dope exited with -1" or something like that. I will try to reproduce that error or is this known already?
This issue is not known to me. It would be very helpful to have more information on this. Are you using the plain text console of L4Linux? How do you start DOpE (Grub or Loader)? Are you using Fiasco-UX or Fiasco on bare hardware? Which libC are you using? Which program prints the error message? Reproducing the error would help a lot.
Regards,
Norman Feske
Hi Norman,
This issue is not known to me. It would be very helpful to have more information on this. Are you using the plain text console of L4Linux?
L4Linux (2.6.13)
How do you start DOpE (Grub or Loader)?
title=-= ( Fiasco mit DoPe und L4Linux )=- kernel (nd)/v2bins/bootstrap modaddr 0x06000000 module (nd)/fiasco -nokdb -serial -comport 1 -comspeed 115200 -nowait module (nd)/v2bins/sigma0 module (nd)/v2bins/roottask -sigma0 task modname "bmodfs" module module module module module module task modname "l4dope" boot_priority 0xA8 module (nd)/v2bins/names module (nd)/v2bins/dmon module (nd)/v2bins/dm_phys module (nd)/v2bins/simple_ts -t 380 module (nd)/v2bins/rtc module (nd)/v2bins/l4io --noirq module (nd)/v2bins/bmodfs module (nd)/cfg/run.bmodfs.cfg module (nd)/v2bins/run module (nd)/v2bins/libloader.s.so module (nd)/vmlinuz26 module (nd)/cfg/l4linux26ramdisk.cfg module (nd)/ramdisk module (nd)/v2bins/l4exec module (nd)/v2bins/l4dope --l4io module (nd)/v2bins/loader --fprov=BMODFS l4linux26ramdisk.cfg vbeset 0x117
Are you using Fiasco-UX or Fiasco on bare hardware?
Fiasco on real hardware
Which libC are you using?
2.3.5-r2
Which program prints the error message?
hmm, sorry, I can't remember...
Reproducing the error would help a lot.
I tried it again today by producing lots of output by simply "cat /dev/urandom", but that didn't reproduce the error. I also tried to recompile the application which led to the error yesterday, but now it went through smoothly, so its probably been just a strange coincidence
Thanks anyway,
Marcel
l4-hackers@os.inf.tu-dresden.de