Open slyrus opened 4 years ago
What version and what way to build / install Jack are you using?
Is there a pattern that you recognized on when it happens, after how long, or depending on the workload?
I am using the latest develop branch from git: dc6c9959 I build/install as follows:
export WAFOPTS=--jobs=32
CFLAGS="-O3" ./waf configure
CFLAGS="-O3" ./waf ${WAFOPTS}
sudo ./waf install
I start jack with qjackctl on startup.
It usually happens after a day or two when I'm away from the keyboard, but have left jackd/guitarix/ardour running, as I usually do.
OP mentions jackd as top process but the copy paste shows irq? I might be wrong, but I dont think jack can cause hang in irq, irq passes a signal to jack via alsa and is released, jack polls on alsa fd in a separate process
therefore it may be worthwhile to do a duration test without jack, using arecord + aplay to rule out issues with the audio interface
Using the stock ubuntu studio PREEMPT kernel (Linux 5.8.0-26-lowlatency #27-Ubuntu SMP PREEMPT Thu Oct 22 00:13:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux), I fairly reliably see jackd hanging and pegging a CPU. If I run top, I see something like the following:
htop shows jackd as the top process or two and jackd is wedged.
I'm running ardour and guitarix and have a jackd/pulseaudio setup that I'd be happy to describe in more detail, and a Steinberg UR44 audio interface.
Any suggestions on how to go about tracking this down?