LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Muni Sekhar <munisekharrms@gmail.com>,
	alsa-devel <alsa-devel@alsa-project.org>,
	linux-usb@vger.kernel.org, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: USB-Audio: Device or resource busy (strace log)
Date: Wed, 11 Aug 2021 14:46:20 +0200	[thread overview]
Message-ID: <41bebccc-7940-8379-0108-047bd1cc92f9@perex.cz> (raw)
In-Reply-To: <CAHhAz+hQBnUVWBnoQO6y44C-G5CnZdFLJ7v738_Y5Rt6AZSkrA@mail.gmail.com>

On 11. 08. 21 14:36, Muni Sekhar wrote:
> Hi All,
> 
> $ cat /proc/asound/cards
>  0 [USB            ]: USB-Audio - Plantronics .Audio 628 USB
>                       Plantronics Plantronics .Audio 628 USB at
> usb-0000:00:14.0-2, full speed
> 
> I am using a Plantronics USB Audio headset.
> 
> $ arecord --device hw:0,0 --channels 2 --format S16_LE --rate 44100Hz x.wav
> arecord: main:722: audio open error: Device or resource busy
> 
> 
> 'arecord' command always fails the first time after system boot in my
> system. But subsequent execution of the 'arecord' command runs fine.
> 
> 
> I've attached the strace log for the "audio open error: Device or
> resource busy" failure. Is there any fix available for this issue?

You may check which other task blocks the PCM device:

  lsof /dev/snd/pcmC0D0c

I guess that it will be pulseaudio (device enumeration).

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

  reply	other threads:[~2021-08-11 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 12:36 Muni Sekhar
2021-08-11 12:46 ` Jaroslav Kysela [this message]
     [not found]   ` <CACk2A5ZcrVTv4AVHdmRDh-xWkx=1BHi6SV8yYqX1Z2DzcDR8hA@mail.gmail.com>
2021-08-11 13:18     ` Muni Sekhar
2021-08-13 16:29       ` Muni Sekhar

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=41bebccc-7940-8379-0108-047bd1cc92f9@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=munisekharrms@gmail.com \
    --subject='Re: USB-Audio: Device or resource busy (strace log)' \
    /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

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).