I think I found a subtle bug in CONDITION-WAIT and deadlines:
Let's say the FUTEX-WAIT in CONDITION-WAIT's definition returns due to
After the return of FUTEX-WAIT, the mutex is reaquired.
Notice, however, that GET-MUTEX may involve signaling due to
exhaustion of the current deadline!
Let's say that deadline is signaled there, and defered in the handler.
We return from GET-MUTEX back into CONDITION-WAIT,
get into the (1) clause of the CASE due to FUTEX-WAIT's previous
and signal the old deadline _again_!!!
At least that's how I explain a failure that I'm currently seeing.
I'll try to come up with an independent test case, and a patch in the