alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Arun Raghavan <arun.raghavan@collabora.co.uk>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Event flood on USB disconnect
Date: Sat, 01 Oct 2011 14:19:42 +0530	[thread overview]
Message-ID: <1317459007.6559.18.camel@snowflake> (raw)

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
one machine or one USB headset, and I'm running kernel 3.0.4

I'm basically seeing a flood of events on the mixer pollfds (goes as
high as 4+ million of them). As far as I can tell, they all contain
(POLLERR|POLLNVAL). From a preliminary look at the code this seems to be
expected on a card disconnect, but I assume not so often.

I'm going to try to handle this by just stopping PA from listening on
these fds when I get a (POLLERR|POLLNVAL), but it seems to me that this
is a bug in the driver somewhere. Any ideas w.r.t. what might be going
wrong or where I should be looking to debug further?

Cheers,
Arun

             reply	other threads:[~2011-10-01  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-01  8:49 Arun Raghavan [this message]
2011-10-01  8:53 ` Event flood on USB disconnect Arun Raghavan
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=1317459007.6559.18.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).