From: "Chris Rankin" <rankincj@yahoo.com>
To: alsa-devel@lists.sourceforge.net
Subject: "Cannot allocate memory" problem with latest CVS
Date: Sun, 27 Oct 2002 18:05:41 +0000 (GMT) [thread overview]
Message-ID: <20021027180541.43540.qmail@web40608.mail.yahoo.com> (raw)
Hi,
The 'cannot allocate memory' problem has returned on
my machine:
$ aplay /usr/lib/sounds/ring.wav
Playing WAVE '/usr/lib/sounds/ring.wav' : Unsigned 8
bit, Rate 22050 Hz, Mono
ALSA lib pcm_hw.c:297:(snd_pcm_hw_hw_params)
SNDRV_PCM_IOCTL_HW_PARAMS failed: Cannot allocate
memory
aplay: set_params:814: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: U8
SUBFORMAT: STD
SAMPLE_BITS: 8
FRAME_BITS: 8
CHANNELS: 1
RATE: 22050
PERIOD_TIME: 100000
PERIOD_SIZE: 2205
PERIOD_BYTES: 2205
PERIODS: 5
BUFFER_TIME: 500000
BUFFER_SIZE: 11025
BUFFER_BYTES: 11025
TICK_TIME: 10000
$ 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:297:(snd_pcm_hw_hw_params)
SNDRV_PCM_IOCTL_HW_PARAMS failed: Cannot allocate
memory
aplay: set_params:814: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: S16_LE
SUBFORMAT: STD
SAMPLE_BITS: 16
FRAME_BITS: 32
CHANNELS: 2
RATE: 22050
PERIOD_TIME: 100000
PERIOD_SIZE: 2205
PERIOD_BYTES: 8820
PERIODS: 5
BUFFER_TIME: 500000
BUFFER_SIZE: 11025
BUFFER_BYTES: 44100
TICK_TIME: 10000
$ aplay /usr/lib/sounds/star_trek_6_overture.au
Playing Sparc Audio
'/usr/lib/sounds/star_trek_6_overture.au' : Mu-Law,
Rate 8000 Hz, Mono
ALSA lib pcm_hw.c:297:(snd_pcm_hw_hw_params)
SNDRV_PCM_IOCTL_HW_PARAMS failed: Cannot allocate
memory
aplay: set_params:814: Unable to install hw params:
ACCESS: RW_INTERLEAVED
FORMAT: MU_LAW
SUBFORMAT: STD
SAMPLE_BITS: 8
FRAME_BITS: 8
CHANNELS: 1
RATE: 8000
PERIOD_TIME: 125000
PERIOD_SIZE: 1000
PERIOD_BYTES: 1000
PERIODS: 4
BUFFER_TIME: 500000
BUFFER_SIZE: 4000
BUFFER_BYTES: 4000
TICK_TIME: 10000
$ free -t
total used free shared
buffers cached
Mem: 1033544 1020348 13196 0
30228 748684
-/+ buffers/cache: 241436 792108
Swap: 498004 10668 487336
Total: 1531548 1031016 500532
$ vmstat
procs memory swap
io system cpu
r b w swpd free buff cache si so bi
bo in cs us sy id
2 0 0 10668 13096 30284 748728 0 0 1
3 10 14 97 3 0
I am using the snd-emu10k1 driver with a SB-Live!
card, on a 2.4.19-SMP box with 1 GB memory, so this
out-of-memory error is a bit of a mystery. Are there
any other statistics that would be useful? I expect
(hope!) that this error will disappear soon, so I'd
recommend a swift response, if required.
Cheers,
Chris
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
next reply other threads:[~2002-10-27 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 18:05 Chris Rankin [this message]
2002-10-28 12:08 ` "Cannot allocate memory" problem with latest CVS Takashi Iwai
2002-10-28 13:21 ` Chris Rankin
2002-10-28 15:15 ` Takashi Iwai
2002-10-28 20:26 ` Chris Rankin
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=20021027180541.43540.qmail@web40608.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=alsa-devel@lists.sourceforge.net \
/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.