Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Laurent POIROT" <Laurent@medianet-usa.com>
To: linux-sound@vger.kernel.org
Subject: Sound Recoder Error: could not allocate DMA buffer
Date: Tue, 13 Jul 1999 12:23:21 +0000	[thread overview]
Message-ID: <marc-linux-sound-92910291824453@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92912084111654@msgid-missing>

After several recordings of wav files with wavrec, i have this Sound Recoder
Error: could not allocate DMA buffer that comes out. I have no idea when
this come from. I use a crontab to make a recording from that soundcard for
5 minutes on a wav file and i do that every 30 minutes. It works perfectly
for a while until this error, if you have any idea, please let me know. I
use Linux Redhat 5.2 with a SoundBlaster Pro ISA. Do you think that changing
the sound card would change this problem ?

thanks

      parent reply	other threads:[~1999-07-13 12:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-11 16:35 Sound Recoder Error: could not allocate DMA buffer Jeremy Hall
1999-06-11 17:55 ` Kevin Turner
1999-07-13 12:23 ` Laurent POIROT [this message]

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=marc-linux-sound-92910291824453@msgid-missing \
    --to=laurent@medianet-usa.com \
    --cc=linux-sound@vger.kernel.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