[prev in list] [next in list] [prev in thread] [next in thread]
List: linux-audio-dev
Subject: Re: [LAD] snd-usb-audio dying on jackd xruns
From: Rods Bobavich <rodnisms () gmail ! com>
Date: 2011-02-03 15:44:20
Message-ID: AANLkTinxfVDFB-dbFZV6vENaDV+K+RpyzEHUq1bT+Xaq () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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 <clemens@ladisch.de> wrote:
> Rods Bobavich wrote:
> > 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.
>
[Attachment #5 (text/html)]
<div dir="ltr">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...<div><br></div><div>I'll still run debug on this and report. Which \
kernel did you want me to test?<br clear="all">
<div dir="ltr"><br>...Rods ;-)<br><br></div><br><div class="gmail_quote">On Thu, Feb \
3, 2011 at 01:22, Clemens Ladisch <span dir="ltr"><<a \
href="mailto:clemens@ladisch.de">clemens@ladisch.de</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;">
<div class="im">Rods Bobavich wrote:<br>
> USB interface is any one of the M-Audio Line. FastTrack USB, FastTrack Pro,<br>
> MobilePre USB... In other words multiple interfaces have been tested. This<br>
> problem is specific to this machine...<br>
><br>
</div><div class="im">> ALSA urb.c:480: frame 0 active: -75<br>
<br>
</div>Thank you for not mentioning this message on alsa-devel.<br>
<br>
In the context of USB, the error code -75 means "babble", which is<br>
a technical term from the USB specification that means that the device<br>
sent some data at a time when it shouldn't (or at least the controller<br>
thinks so).<br>
<div class="im"><br>
> ALSA urb.c:146: timeout: still 7 active urbs..<br>
</div><div class="im">> ALSA urb.c:146: timeout: still 2 active urbs..<br>
</div><div class="im">> ALSA pcm.c:223: 4:2:1: usb_set_interface failed<br>
<br>
</div>As a result of that, the USB controller driver gets wedged.<br>
<br>
<br>
This looks like a hardware problem with your USB controller. Please try<br>
the latest kernel; there were added some workarounds recently.<br>
<br>
You might also try connecting the device through a hub (but there are<br>
some bugs in the EHCI driver which might make it think that it cannot<br>
schedule enough bandwidth for full duplex).<br>
<br>
<br>
> CE: hpet increased min_delta_ns to 7500 nsec<br>
><br>
> It seems that the error happened about the time of the hpet increase. Do we<br>
> have a timer problem?<br>
<br>
No, this has nothing to do with USB. This message typically occurs on<br>
AMD system with C1E enabled, and is harmless.<br>
<br>
<br>
Regards,<br>
Clemens<br>
<font color="#888888">--<br>
Don't anthropomorphize computers; they don't like it.<br>
</font></blockquote></div><br></div></div>
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic