-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jackd hangs with JackAudioDriver::ProcessGraphAsyncMaster process error after boot #50
Comments
not 100% reproducible, happened two out of three boots so far. |
|
same issue on AMP4/RPI4 |
Usually not self-recovering. Killing mod-host helps most of the time, but not always. |
Funny: is this the race condition I'm seeing? There is a jack_lsp job running in parallel...
This was the first time such a message occurred. EDIT: since observed two more times, out of some 20 reboots. |
It looks like jack client creation and/or jack_lsp is racy and can send jackd into this death spiral. After reintroducing waiting for ports, the issue seems to have disappeared or at least become so rare that I haven't observed it since. Needs to be looked at further. See commits c214689 and 4f55138 . |
It still happens when the boot process is stalled because of an fsck or because systemd-timesyncd stalls and then syncs, at which point all Jack clients are long ready and spinning on mn_jack_wait or mn_jack_connect, which seems to trigger the death spiral. |
Not observed since. |
again observed several times on bookworm, only ever with the mod-monitor client. |
then recovers after > 1min.
May 15 21:42:26 mn-Dantax jackd[643]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
May 15 21:42:26 mn-Dantax jackd[643]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
May 15 21:42:26 mn-Dantax jackd[643]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
[repeats hundreds of times, many per second]
Hardware is Pi4 with DAC+ADC with AMP60 on top, kernel 4.19.97
System software: Raspbian GNU/Linux 10 (buster)
medianet overlay: Tue May 5 23:02:49 2020 +0200 b13c3ad
The text was updated successfully, but these errors were encountered: