[PlanetCCRMA] Problems after starting Jack on Fedora 19

[Niclas Hoyer]

Hi,

I've got some problems starting Jack and I'm a little helpless. 
Sometimes it works, but most of the time I get strange errors.

The soundcard I'm using is a "Creative Sound Blaster Audigy SE" (PCI) 
[1], while it is not very high priced it seems very well supported by ALSA.

Output of lspci:
$ lspci | grep Sound
04:06.0 Multimedia audio controller: Creative Labs CA0106 Soundblaster

Output of aplay -l appended at the bottom [5].

I'm running a fully updated Fedora 19, x86_64 with CCRMA repos enabled, 
and I've got the latest rt kernel installed:
$ uname -a
Linux localhost.localdomain 3.10.15-200.rt11.1.fc19.ccrma.x86_64.rt #1 
SMP PREEMPT RT Fri Oct 11 17:02:17 PDT 2013 x86_64 x86_64 x86_64 GNU/Linux

I verified that neither PulseAudio or Jack are running:
$ ps -A | grep pulse
$ ps -A | grep jack

Jack seems to start successfully roughly on every 30th attempt. And 
after some time it seems that it will never work again until reboot. The 
command line I'm using is:
jackd -v -P 90 -dalsa -dhw:CA0106,0 -r44100 -p128 -n2

usually I get the following output:
$ jackd -v -P 90 -dalsa -dhw:CA0106,0 -r44100 -p128 -n2
jackdmp 1.9.9.5
[...]
Jack: JackPosixThread::ThreadHandler : start
Jack: JackSocketServerChannel::ClientCreate socket
Jack: JackSocketServerChannel::BuildPoolTable size = 2
Jack: JackSocketServerChannel::BuildPoolTable fSocketTable i = 1 fd = 9
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: ALSA XRun wait_status = 0
...

the last lines then repeat over and over again. For the full log see [2].
I get the same output even if I disable realtime, use the default Fedora 
kernel or using higher period time:
jackd -v -r -dalsa -dhw:CA0106,0 -r44100 -p1024 -n2

Sometimes the device CA0106,1 is working, while CA0106,0 does not work. 
CA0106,1 is line out, CA0106,0 is the normal audio output. For a the log 
output of a successful run (usually directly after boot) see [4]. Once 
jack started successfully the server runs mostly smooth and never prints 
the messages I get if it is failing.

Could it be the sound card? What could I try to determine the problem? 
It seems to be randomly failing most of the time.

I collected all modifications to my plain Fedora 19 installation in 
another gist [3].

I'm happy if anyone is willing to help. I'll also buy a new sound card 
if that is the problem after all.

Regards,
Niclas

[1] 
http://us.store.creative.com/Creative-Sound-Blaster-Audigy-SE-PCI/M/B000LP0R3E.htm
[2] https://gist.github.com/niclashoyer/0e55eb77bd4cf4207363
[3] https://gist.github.com/niclashoyer/7124643
[4] https://gist.github.com/niclashoyer/6e4a4364240e05d019b7
[5]
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: CA0106 [CA0106], device 0: ca0106 [CA0106]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 0: CA0106 [CA0106], device 1: ca0106 [CA0106]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 0: CA0106 [CA0106], device 2: ca0106 [CA0106]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
card 0: CA0106 [CA0106], device 3: ca0106 [CA0106]
   Subdevices: 1/1
   Subdevice #0: subdevice #0