7 Jan
2003
7 Jan
'03
10:32 p.m.
So I run that in a terminal and after playing around
with a bunch of
jack apps got the machine to lockup... and then, after a little bit,
suddenly, it came back to life! (you could see that the monitor had
changed the priority of the hogs to SCHED_OTHER).
So I guess that somehow jack has a hard to trigger race condition that
locks up the machine when running SCHED_FIFO.
Now I have to figure out how to trace the thing so as to determine where
the whole thing is locking. Help from the jack gurus appreciated.
what do you want to know? can you get roger's tool to tell you which
process (PID) is hogging the CPU? is it jackd or a client?
--p