From: Takashi Iwai <tiwai@suse.de>
To: Mark Knecht <markknecht@attbi.com>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
Date: Wed, 21 May 2003 13:09:34 +0200 [thread overview]
Message-ID: <s5haddgv9n5.wl@alsa2.suse.de> (raw)
In-Reply-To: <1053302732.1749.6.camel@Wizard.knechthome.com>
At 18 May 2003 17:05:32 -0700,
Mark Knecht wrote:
>
> Hi,
> I brought up Alsa Friday on a Gentoo platform and used it for most of
> Friday evening and Saturday in one form or another. Along the way I was
> building some new kernels to fix some SCSI issues and a few other items,
> which required that Alsa get rebuilt also as per the Gentoo Alsa
> instructions. This process went on for most of the day. Later Saturday
> evening, following who knows how many 'unrelated' changes, Alsa stopped
> working. The error messages look like this:
>
> Wizard root # aplay wave/sequen~1.wav
> Playing WAVE 'wave/sequen~1.wav' : Signed 16 bit Little Endian, Rate
> 44100 Hz, Mono
> aplay: pcm_write:1025: write error: Input/output error
> Wizard root #
>
> or when trying to play a game like frozen-bubble, that app locks up hard
> and in my console I see:
>
> ALSA Lib pcm_hw.c:467:(snd_pcm_hw_prepare)SNDRV_PCM_IOCTL_PREPARE
> failed:device or resource busy
>
> alsaplayer starts to run, sees the CD (I.e. - shows track length) and
> then won't play the CD.
>
> I'll attach a bit of data, but can anyone point me toward what might be
> causing this?
the chip looks like a VIA8235, so the (first) pcm device supports
multiple playbacks but with the same sample rate.
please check whether there is any other app running and using the pcm
device and if it uses different sample rates (e.g. 48kHz)...
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-21 11:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 0:05 aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy Mark Knecht
2003-05-21 11:09 ` Takashi Iwai [this message]
2003-05-30 4:43 ` Mark Knecht
2003-06-02 11:11 ` Takashi Iwai
2003-06-02 13:41 ` Mark Knecht
2003-06-02 13:55 ` Takashi Iwai
2003-06-02 14:20 ` Mark Knecht
2003-06-02 14:25 ` Takashi Iwai
2003-06-02 14:33 ` Mark Knecht
2003-06-02 14:46 ` Takashi Iwai
2003-06-03 4:14 ` Mark Knecht
2003-06-02 14:35 ` Mark Knecht
2003-06-02 14:48 ` Takashi Iwai
2003-06-02 14:59 ` Mark Knecht
2003-06-02 14:49 ` David E. Storey
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=s5haddgv9n5.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=markknecht@attbi.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 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.