I meant whether you can see other tasks or threads in kdump that are accessing the sound device. JACK is running with the linked PCM streams, and both playback and capture PCM streams were being accessed when the bug happened, I suppose. If my assumption is right, the other task or thread should be also spinning to take some lock while keeping the spinlock held.