Fernando Pablo Lopez-Lezcano wrote:
...
4)
schedule +1ab
sleep_on +45
bread +20
__mark_inode_dirty +d9
pipe_write +1b9
poll_freewait +44
sys_write +9f
system_call +33
So the system seems to be stuck in __mark_inode_dirty, whatever that is.
No, that's just stack gunk.
There's no
qjackconnect. I'm currently trying to see if I can start the stuff from
the text console so that I can try to catch some register dumps through
the sysrq magic key...
I don't have the time now to analyze the results but it would seem the
problem is freqtweak in combination with jackd.
To add one more datapoint to the thread and (apparently good news): I'm
testing 2.4.20 (final) + lowlat + preempt + acpi + alsa + jack and the
computer seems to be chugging along nicely. This is with today's alsa. A
slighly older alsa did lock the computer after 5 or so minutes of jack
