From: Takashi Iwai <tiwai@suse.de>
To: Chris Rankin <rankincj@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Cannot allocate memory (on a 1GB box???)
Date: Mon, 23 Sep 2002 12:24:39 +0200 [thread overview]
Message-ID: <s5hheghovfc.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020920221440.3880.qmail@web40604.mail.yahoo.com>
At Fri, 20 Sep 2002 23:14:40 +0100 (BST),
Chris Rankin wrote:
>
> Hi,
>
> [Linux 2.4.19-SMP, SB Live!, alsa-lib CVS, alsa-utils
> rc3]
>
> I have just tried to play a WAV file on my machine,
> but have triggered these errors instead. The machine
> didn't crash, fortunately, but it's very irritating to
> have memory problems on a 1 GB machine:
>
> $ aplay /usr/lib/sounds/jungle_exit.wav
> Playing WAVE '/usr/lib/sounds/jungle_exit.wav' :
> Signed 16 bit Little Endian, Rate 22050 Hz, Stereo
> ALSA lib pcm_hw.c:295:(snd_pcm_hw_hw_params)
> SNDRV_PCM_IOCTL_HW_PARAMS failed: Cannot allocate
> memory
(snip)
> It was apparently the 16 bit nature of the WAV file
> which was causing trouble, because I got my sound back
> by playing an 8 bit one instead. It's all very odd.
> Was my memory just momentarily too fragmented for ALSA
> to allocate a big enough DMA buffer?
no, the current emu10k1 driver uses sg-buffer for playback, so the
fragmentation is not the cause.
if this error comes from the buffer allocation, then it means that
page-0 allocation failed. please check the kernel message.
i modified again the pci_alloc_consistent() wrapper. hope the newer
one fixes this bug. a new one tries to allocate pages with the
original dma mask if failed without dma mask.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2002-09-23 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 22:14 Cannot allocate memory (on a 1GB box???) Chris Rankin
2002-09-23 10:24 ` Takashi Iwai [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=s5hheghovfc.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rankincj@yahoo.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.