Thank you Dan!
I do not have access to a FreeBSD computer during this weekend but
your stack prints already tell the origin of the problem.
I have implemented my own mutexes in the purpose that I can use
an assembler instruction for the atomic test-and-set operation
needed in a mutex. But for no
In the last episode (Mar 30), Heikki Tuuri said:
> The FreeBSD bug is known. I will run tests on our FreeBSD machine in
> the next few days. Obviously there is something wrong with the
> FreeBSD port. Was it so that it hung and used 100 % of CPU? That has
> been reported also from Italy.
I have a
