From: Mark_H_Johnson@Raytheon.com
To: Lee Revell <rlrevell@joe-job.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Takashi Iwai <tiwai@suse.de>,
Andrew Morton <akpm@osdl.org>,
alsa-devel@alsa-project.org, Adrian Bunk <bunk@stusta.de>,
lkml <linux-kernel@vger.kernel.org>,
perex@suse.cz
Subject: Re: [Alsa-devel] Re: 2.6.10-mm1: ALSA ac97 compile error with CONFIG_PM=n
Date: Fri, 7 Jan 2005 08:41:51 -0600 [thread overview]
Message-ID: <OF54D6A36A.84E8AEAC-ON86256F82.0050BC7F-86256F82.0050BCA9@raytheon.com> (raw)
> And if you want to find out who is using it then try fuser /dev/dsp,
> fuser /dev/snd/*, or lsof.
Hmm. I figured out which application is "getting in my way" but am not
quite sure why I have a problem opening the audio / what I should do
about it.
On my system...
# fuser /dev/snd/* /dev/dsp
/dev/snd/pcmC0D0p: 2972 2972m
# ps -fe | grep 2972
u21305 2972 2936 0 10:15 ? 00:00:02 artsd -F 10 -S 4096 -a alsa
-s 60 -m artsmessage -c drkonqi -l 3 -f
root 4915 3407 0 11:08 pts/7 00:00:00 grep 2972
# fuser /dev/snd/* /dev/dsp
[I caused a console beep here using backspace]
# fuser /dev/snd/* /dev/dsp
/dev/snd/pcmC0D0p: 2972 2972m
OK, so artsd wakes up on some trigger and then waits around a while
expecting to get some more audio to process. I see it is a user of
/dev/snd/pcmC0D0p but not a user of /dev/dsp. Yet when I attempt to
open /dev/dsp, I get an error.
When I successfully run latencytest (and open /dev/dsp) I see...
# fuser /dev/snd/* /dev/dsp
/dev/dsp: 9156
which is the pid of latencytest.
Can someone please explain the relationship between these devices
and why access to one of these devices prevents access to another?
This is certainly confusing to me.
Thanks.
--Mark
next reply other threads:[~2005-01-07 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 14:41 Mark_H_Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-05 18:15 [Alsa-devel] Re: 2.6.10-mm1: ALSA ac97 compile error with CONFIG_PM=n Mark_H_Johnson
2005-01-05 14:21 Mark_H_Johnson
2005-01-05 14:56 ` Alan Cox
2005-01-05 17:23 ` Lee Revell
2005-01-05 16:49 ` Takashi Iwai
2005-01-05 18:04 ` Lee Revell
2005-01-04 19:25 Mark_H_Johnson
2005-01-05 13:41 ` [Alsa-devel] " Takashi Iwai
2005-01-05 21:27 ` Andrew Morton
2005-01-05 21:43 ` Lee Revell
2005-01-06 16:30 ` Alan Cox
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=OF54D6A36A.84E8AEAC-ON86256F82.0050BC7F-86256F82.0050BCA9@raytheon.com \
--to=mark_h_johnson@raytheon.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.com \
--cc=tiwai@suse.de \
/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).