From: "Christopher Montgomery" <xiphmont@gmail.com>
To: "Ian Stirling" <tandra@mauve.plus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] USB snd-usb-audio wedges lsusb when unplugged while playing sound.
Date: Sat, 22 Jul 2006 12:49:22 -0400 [thread overview]
Message-ID: <806dafc20607220949y4ebbc88av99e0e689e1fd687e@mail.gmail.com> (raw)
In-Reply-To: <44C21635.5090808@mauve.plus.com>
On 7/22/06, Ian Stirling <tandra@mauve.plus.com> wrote:
> Config/... as my earlier message on USB - though with the bandwidth
> enforcement
> turned off so it actually plays sound, when plugged into the USB1 port.
>
> 2.6.17.
>
> Basically - playing sound with
> mplayer -ao alsa:device=hw=1 or whatever - and then unplugging the
> soundcard completely wedges lsusb/usb configuration, until the mplayer
> process is killed.
This sounds like the well known EPIPE problem in usb-audio and one I
intended to fix after dealing with the ehci scheduler.
It boils down to this: although the low-level usb code is properly
reporting and distinguishing error conditions, usb-audio translates
just about everything that goes wrong into 'EPIPE'. Because an
application has no way to distinguish temporary from permanent errors
(and the coding docs specify that the app resubmit), it immediately
retries and gets another EPIPE. This infinite retry loop places
enough system load on the machine that it may well even stop pinging.
Although the *machine* is not wedged, if this happens in a realtime
thread (eg, jack using a usb-audio device), it may well be hosed
enough to become unrecoverable.
Monty
next prev parent reply other threads:[~2006-07-22 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 12:12 Ian Stirling
2006-07-22 15:44 ` Andrew Morton
2006-07-22 16:20 ` Ian Stirling
2006-07-22 16:49 ` Christopher Montgomery [this message]
2006-07-22 17:00 ` [linux-usb-devel] " Ian Stirling
2006-07-22 17:04 ` Christopher Montgomery
2006-07-22 23:52 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=806dafc20607220949y4ebbc88av99e0e689e1fd687e@mail.gmail.com \
--to=xiphmont@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tandra@mauve.plus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®