Content-Type: text/plain; charset=UTF-8
I got a new PCI USB 2.0 card and now I'm running Jackd at -n2 -p64. I
figured this was a hardware glitch. Thanks for confirming...
I'll still run debug on this and report. Which kernel did you want me to
On Thu, Feb 3, 2011 at 01:22, Clemens Ladisch wrote:
> Rods Bobavich wrote:
Content-Type: text/html; charset=UTF-8
I got a new PCI USB 2.0 card and now I'm running Jackd=
at -n2 -p64. I figured this was a hardware glitch. Thanks for confirming..=
.I'll still run debug on this and report. Which ker=
nel did you want me to test?
...Rods ;-)On Thu, Feb 3, 2011 at 01:22, Clemens Ladisch <firstname.lastname@example.org> wrote:
Rods Bobavich wrote:
Thank you for not mentioning this message on alsa-devel.
In the context of USB, the error code -75 means "babble", which i=
a technical term from the USB specification that means that the device
sent some data at a time when it shouldn't (or at least the controller<=
> ALSA urb.c:146: timeout: still 7 active urbs..
> ALSA pcm.c:223: 4:2:1: usb_set_interface faile=
As a result of that, the USB controller driver gets wedged.
This looks like a hardware problem with your USB controller. =C2=A0Please t=
the latest kernel; there were added some workarounds recently.
You might also try connecting the device through a hub (but there are
some bugs in the EHCI driver which might make it think that it cannot
schedule enough bandwidth for full duplex).
> CE: hpet increased min_delta_ns to 7500 nsec
No, this has nothing to do with USB. =C2=A0This message typically occurs on=
AMD system with C1E enabled, and is harmless.
Don't anthropomorphize computers; they don't like it.