[BUG] Deadlock in Fiasco kernel

Bjoern Doebel doebel at os.inf.tu-dresden.de
Tue Mar 6 12:59:20 CET 2007

Hash: SHA1

Hi Daniel,

> I noticed that the Fiasco kernel hangs under some circumstances so the
> whole system stops working. Unfortunately I wasn't even able to enter
> the kernel debugger via a serial cable in this case. The error is
> reproducible on different plattforms (e.g. Thinkpad T43, 1GB RAM,
> Pentium M 1.8 GHz or Thinkpad T41) even though it only appears from time
> to time (probability ~50% or even better). Within VMWare or Qemu this
> deadlock does *not* appear. Furthermore this error does not occur if the
> kernel was started using the "-esc" option. I wasn't able to reproduce
> this bug on a HP nx7400 (Dual Core T2300, 1GB RAM).
> We use an own dynamic loader to load some L4 tasks whereas other L4
> tasks, as the mGUI, are loaded by GRUB.
> The bug can be reproduced on real hardware using the iso-image which I
> will upload to the SLOX server (deadlock.iso). You have to choose GRUB
> entry two or three. If the error occurs the system hangs in text mode
> otherwise a graphical mode is entered. Sometimes you have to reboot up
> to 20 times but it usually occurs immediately.

After some (~ 10) tries I can ackowledge your problem. However I'm afraid
we won't be able to help you without further information.

Please find attached our bugreport form and fill in the missing information.

Note, that we do not have any access to some of the applications in your
scenario, namely
- - randservice
- - storage
- - hddenc
- - pmngr
- - mgui
- - compmgr
- - compmgrclientl4
- - maybe loader, if this is not identical to the loader which is part of the

To get help, you should either
* reproduce the problem with components coming only from the OTC snapshot
used for your scenario, or
* provide us with source code of the participating applications so that we
are able to debug all parts of the system.

Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bugreport.txt
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20070306/4418e14e/attachment-0001.txt>

More information about the l4-hackers mailing list