Jack crashes and consumes 100% CPU after resume from suspend

Bug #659025 reported by Johannes H. Jensen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libffado (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Suspending my computer with jackd running causes jackd to go into an infinite loop when computer is resumed again. It consumes 100% of the cpu and freezes the system for a short period, producing an endless stream of the following messages:

firewire ERR: wait status < 0! (= -1)
JackAudioDriver::ProcessAsync: read error, skip cycle
JackFFADODriver::ffado_driver_wait - unhandled xrun
firewire ERR: wait status < 0! (= -1)
JackAudioDriver::ProcessAsync: read error, skip cycle
JackFFADODriver::ffado_driver_wait - unhandled xrun
firewire ERR: wait status < 0! (= -1)
JackAudioDriver::ProcessAsync: read error, skip cycle
JackFFADODriver::ffado_driver_wait - unhandled xrun

I'm using jackd2 (1.9.5~dfsg-19ubuntu1) and jackd2-firewire (1.9.5~dfsg-19ubuntu1). My sound card is an Edirol FA-66.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libffado2 2.0.1+svn1856-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Oct 12 10:23:01 2010
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: libffado

Revision history for this message
Johannes H. Jensen (joh) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libffado (Ubuntu):
status: New → Confirmed
Revision history for this message
intuited (intuited) wrote :

I can't confirm the error messages, but I'm seeing this or similar behaviour on two different machines. One is running 10.10 amd64; the other, 11.10 i386. Both are using the default `jackd2` package.

This bug really reduces the practicality of using jack on a laptop, since it's much more convenient to leave things running when moving than it is to shut everything down. It's also inconvenient for people who like to conserve electricity by suspending their machines when they are not in use.

Revision history for this message
intuited (intuited) wrote :

Confirmed that removing the package `jackd2-firewire` does not help with this issue.

Revision history for this message
intuited (intuited) wrote :

Using jackd1 instead of jackd2 seems to be a workaround.

Revision history for this message
Pander (pander) wrote :

From FFADO maintainer:

   Bug: Jack crashes and consumes 100% CPU after resume from suspend

   Suggestion:
       FFADO was not set up to deal cleanly with suspend and resume, mainly
       because the nature of Firewire interfaces makes this a very difficult
       problem to solve. In particular, the device itself exists outside of
       the suspend infrastructure so FFADO has no guarantee about the
       device's status when a resume occurs. In fact, because of the way
       firewire audio devices work, the streaming would need to be formally
       shut down before suspend and restarted on resume. Jackd's design
       does not lend itself to doing this (although it could perhaps be
       achieved with sufficient time and effort).

       Interestingly, a follow up comment in 2012 suggested that jack1 dealt
       with suspend-resume better than jack2.

       A partial solution to the issue of shutting jackd down before suspend
       may be one of the jack session managers which have since been
       developed. At this stage it is unlikely that FFADO will gain formal
       support for suspend/resume unless someone steps up to write the code.
       I am unsure how many people would make use of such a feature if it
       were to be implemented.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.