linuxaudio.org

--90e6ba5bbb61cdbdbf049b62a4a5

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

test?
...Rods ;-)
On Thu, Feb 3, 2011 at 01:22, Clemens Ladisch  wrote:
> Rods Bobavich wrote:

quoted text
> > USB interface is any one of the M-Audio Line. FastTrack USB, FastTrack

> Pro,

> > MobilePre USB... In other words multiple interfaces have been tested.

> This

> > problem is specific to this machine...

> >

> > ALSA urb.c:480: frame 0 active: -75

>

> Thank you for not mentioning this message on alsa-devel.

>

> In the context of USB, the error code -75 means "babble", which is

> 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

> thinks so).

>

> > ALSA urb.c:146: timeout: still 7 active urbs..

> > ALSA urb.c:146: timeout: still 2 active urbs..

> > ALSA pcm.c:223: 4:2:1: usb_set_interface failed

>

> As a result of that, the USB controller driver gets wedged.

>

>

> This looks like a hardware problem with your USB controller.  Please try

> 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

> >

> > It seems that the error happened about the time of the hpet increase. Do

> we

> > have a timer problem?

>

> No, this has nothing to do with USB.  This message typically occurs on

> AMD system with C1E enabled, and is harmless.

>

>

> Regards,

> Clemens

> --

> Don't anthropomorphize computers; they don't like it.

>

--90e6ba5bbb61cdbdbf049b62a4a5

Content-Type: text/html; charset=UTF-8

Content-Transfer-Encoding: quoted-printable
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 <clemens@ladisch.de> wrote:
Rods Bobavich wrote:

quoted text
> USB interface is any one of the M-Audio Line. FastTrack USB, FastTrack=

 Pro,

quoted text
> MobilePre USB... In other words multiple interfaces have been tested. =

This

quoted text
> problem is specific to this machine...

>

> ALSA urb.c:480: frame 0 active: -75

Thank you for not mentioning this message on alsa-devel.
In the context of USB, the error code -75 means "babble", which i=

s

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<=

br>

thinks so).
> ALSA urb.c:146: timeout: still 7 active urbs..

quoted text
> ALSA urb.c:146: timeout: still 2 active urbs..=

> ALSA pcm.c:223: 4:2:1: usb_set_interface faile=

d
As a result of that, the USB controller driver gets wedged.
This looks like a hardware problem with your USB controller. =C2=A0Please t=

ry

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

quoted text
>

> It seems that the error happened about the time of the hpet increase. =

Do we

quoted text
> have a timer problem?

No, this has nothing to do with USB. =C2=A0This message typically occurs on=
AMD system with C1E enabled, and is harmless.
Regards,

Clemens

--

Don't anthropomorphize computers; they don't like it.
--90e6ba5bbb61cdbdbf049b62a4a5--