From: "Chris Rankin" <rankincj@yahoo.com>
To: alsa-devel@lists.sourceforge.net
Subject: Memory problems are back with SB Live!
Date: Tue, 19 Nov 2002 21:55:16 +0000 (GMT) [thread overview]
Message-ID: <20021119215516.8350.qmail@web40606.mail.yahoo.com> (raw)
Hi,
My box has now accumulated almost 3 weeks of uptime,
and so the ALSA memory problem is back again:
$ 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
Is that patch you sent me to hack^Wfix this still
relevant, or will it make things worse? I've noticed a
few changes to these parts of the kernel drivers.
As an aside, my memory looks like this:
$ free -t
total used free shared
buffers cached
Mem: 1033544 1011004 22540 0
53776 728244
-/+ buffers/cache: 228984 804560
Swap: 498004 8168 489836
Total: 1531548 1019172 512376
Isn't Linux supposed to surrender disk-cache memory if
another process requests it? Surely *some* of that
1011004 KB cache must be usable!?
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: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
next reply other threads:[~2002-11-19 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 21:55 Chris Rankin [this message]
2002-11-28 16:48 ` Memory problems are back with SB Live! Takashi Iwai
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=20021119215516.8350.qmail@web40606.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox