From: Arun Raghavan <arun.raghavan@collabora.co.uk>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Event flood on USB disconnect
Date: Sat, 01 Oct 2011 14:23:39 +0530 [thread overview]
Message-ID: <1317459237.6559.20.camel@snowflake> (raw)
In-Reply-To: <1317459007.6559.18.camel@snowflake>
On Sat, 2011-10-01 at 14:19 +0530, Arun Raghavan wrote:
> Hi folks,
> We're seeing a problem when disconnecting USB headsets in PulseAudio.
> Steps to reproduce are basically: start PulseAudio, plug in USB device,
> wait for it to suspend (pcm is closed but mixer is not), disconnect.
> Fairly often, this results in PA getting killed because the polling
> thread is realtime and exceeds its rlimit. The problem is not limited to
Missed one detail -- I've only seen this happen on the alsa-source
thread, not on alsa-sink, but I've only tested with one device which has
playback as well as capture.
-- Arun
next prev parent reply other threads:[~2011-10-01 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 8:49 Event flood on USB disconnect Arun Raghavan
2011-10-01 8:53 ` Arun Raghavan [this message]
2011-10-04 2:30 ` Raymond Yau
2011-10-04 3:10 ` Arun Raghavan
2011-10-03 8:36 ` Colin Guthrie
2011-10-03 21:50 ` Clemens Ladisch
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=1317459237.6559.20.camel@snowflake \
--to=arun.raghavan@collabora.co.uk \
--cc=alsa-devel@alsa-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.