Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Dave Platt <dplatt@radagast.org>
To: Phil <phillor@telstra.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: /dev/dsp busy
Date: Sun, 31 May 2009 20:29:16 -0700	[thread overview]
Message-ID: <4A234B0C.6010608@radagast.org> (raw)
In-Reply-To: <200906011059.15279.phillor@telstra.com>

Phil wrote:
> Thank you for reading this.
> 
> I've recently upgraded to Mandriva 2009.1 and now none of my 
> Amateur Radio applications will run because /dev/dsp is busy. Yet, 
> "fuser -v dev/dsp" shows that nothing is using the resource.
> 
> I've disabled Pulse Audio in case that was a problem and I don't have 
> any sound applications sitting on the task bar. I had this problem four 
> years ago and that was due to a music player sitting on the task bar.
> 
> The driver in use is: "intel HDA (snd_hda_intel [ALSA])"
> 
> Can anyone offer any suggestions?

It's possible that something is using the ALSA sound
resource path (which is the baseline audio implementation
in modern Linux kernels - the old OSS sound drivers are
deprecated, and /dev/dsp is usually implemented as an ALSA
compatibility driver).

Try "lsof | grep dev/snd" to see what (if anything) is using
the ALSA sound pseudodevices.

Another possibility is that the problem isn't /dev/dsp itself...
rather, it may be that some resource needed by the kernel
to support the sound device is busy (e.g. IRQ or DMA conflict).
I wouldn't think that would be the case with the Intel HDA,
but it's possible that your motherboard BIOS has mapped it
onto the same IRQ which is being used by another device
whose driver doesn't know how to share.


  reply	other threads:[~2009-06-01  3:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01  0:59 /dev/dsp busy Phil
2009-06-01  3:29 ` Dave Platt [this message]
2009-06-01  4:50   ` Phil
2009-06-01  5:38     ` Dave Platt
2009-06-02  2:43       ` Phil

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=4A234B0C.6010608@radagast.org \
    --to=dplatt@radagast.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=phillor@telstra.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