[alsa-devel] Jackd dies with snd-usb-usx2y (DRIVER NT error)
Hi,
I recently upgraded my system from 32-bit Ubuntu Edgy, with a custom hard-realtime-enabled 2.6.19 kernel, to 64-bit Ubuntu Feisty, with a hard-realtime-enabled 2.6.20 kernel. I also switched from an Athlon XP 2600 to an Athlon 64 X2 4600. In every way my new system should be faster, but jackd+usx2y worked on the last system, and doesn't work now.
Here's what I'm doing to test the audio setup:
---------- sudo chrt -f 90 `pidof IRQ-23` # usb irq chrt -v -f 70 jackd -d alsa -dhw:1,2 -p 64 -n 2 # also tried defaults, and values up to -p 256 -n 8 chrt -v -f 25 zynaddsubfx ----------
After a short time (< 1 or 2 minutes) of switching instruments and playing notes with zynaddsubfx, all audio stops and jackd dies with the following error:
---------- ALSA: poll time out, polled for 7998858 usecs DRIVER NT: could not run driver cycle jack main caught signal 12 no message buffer overruns ----------
There is a corresponding message in the kernel log:
---------- [12546.132286] ALSA [...]/usx2yhwdeppcm.c:94: activ frame status -70. Most propably some hardware problem. ----------
I am loading the snd-usb-usx2y module with the nrpacks=1 option. I've gone through the Ubuntu HOWTOs I used to get things working on my last system (to some of which I have even contributed), and I am still having this problem.
I already tried on alsa-user, so I'm taking this to the developer list (since I plan to help fix this if anybody will point me in the right direction).
Additional note: I tried modifying the source code of the driver, commenting out the return statement after the "active status" error message. This began producing a new error message: "shouldn't be here with count=xx". So, I commented out the "return -EPIPE" after that error message, and now jackd doesn't crash. There are noticeable audio clicks whenever one of these errors occurs, but the driver seems to have no problem recovering, as audio continues.
This error happens with the stock Ubuntu kernels as well.
Thanks in advance, Mike Bourgeous
On 5/15/07, Michael Bourgeous sts.nitrogen@gmail.com wrote:
chrt -v -f 70 jackd -d alsa -dhw:1,2 -p 64 -n 2 # also tried defaults,
You should be using jackd -R -d alsa etc. rather than chrt.
chrt -v -f 25 zynaddsubfx
No need to use chrt, jackd will take care of realtime priority.
[12546.132286] ALSA [...]/usx2yhwdeppcm.c:94: activ frame status -70. Most propably some hardware problem.
Sounds like a hardware problem. Try a different USB port. Make sure you aren't using a USB hub.
Lee
participants (2)
-
Lee Revell
-
Michael Bourgeous