Clemens,
USB bug. This is exactly what I thought. Here's a tail of the syslog:
Feb 2 11:04:45 studio1 kernel: [ 997.880412] ALSA pcm.c:226: setting usb interface 2:1 Feb 2 11:04:45 studio1 kernel: [ 997.889440] ALSA pcm.c:226: setting usb interface 1:1 Feb 2 11:05:03 studio1 kernel: [ 1015.338527] CE: hpet increased min_delta_ns to 7500 nsec Feb 2 11:05:28 studio1 kernel: [ 1040.071773] ALSA urb.c:146: timeout: still 7 active urbs.. Feb 2 11:05:34 studio1 kernel: [ 1046.070072] ALSA urb.c:146: timeout: still 2 active urbs.. Feb 2 11:05:56 studio1 kernel: [ 1068.660883] ALSA pcm.c:223: 4:2:1: usb_set_interface failed
It seems that the error happened about the time of the hpet increase. Do we have a timer problem?
...Rods ;-)
On Wed, Feb 2, 2011 at 10:33, Clemens Ladisch clemens@ladisch.de wrote:
Rods Bobavich wrote:
So I start jackd and it runs fine for a while. Then ALSA crashes and triggers an xrun. Jackd continues to do its merry thing - minus the part about spitting info out to my soundcard...
At first I thought this was a Jackd issue but when I looked deeper it
seems
to be ALSA. Once this happens I cannot restart jackd and resume an audio session. In fact, I cannot even rmmod snd-usb-audio. Sometimes I cannot lsusb. So it looks like something is getting seriously hosed!
Looks like a bug in the USB controller driver, probably triggered by some unexpected behaviour of your USB controller.
When this happens, are there any error messages in the system log?
Regards, Clemens