Thanks everyone. It does start to look like a CPU scheduler problem. Other possibilities are that a) Jack is doing something unusual and is triggering some bug in 2.6 which causes the kernel to go into an extended sulk. Or b) Some change in 2.6 is triggering a bug in Jack, causing Jack to go into an extended sulk. Question: have these problems been observed with other audio apps? With a similar severity and frequency? "Jack O'Quin" <joq@xxxxxx> wrote: hm, now here was me thinking the name meant "audio jack" ;) > > ... > > Unfortunately, if you run the JACK daemon as root you must also run > all its clients that way. Maybe Jack could switch UIDs and drop privileges after acquiring rt policy?
