From: "Brian J. Tarricone" <bjt23@ece.cornell.edu>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-user] sb live dma buffer alloc failure?
Date: Fri, 07 Feb 2003 14:46:14 -0500 [thread overview]
Message-ID: <3E440D06.8090803@ece.cornell.edu> (raw)
In-Reply-To: <s5hadh8e23e.wl@alsa2.suse.de>
Takashi Iwai wrote:
>which kernel version are you using?
>
2.4.20 - it's a heavily patched one, tho (out of gentoo's portage).
should i try a vanilla kernel?
>the new code on rc7 simply tries allocation via vmalloc().
>if it fails, it means that the system resource is really exhausted.
>or, there might be memory leak or so...
>
>
hmm... well, rc7 has locked for me very shortly after system startup,
top reports plenty (>200mb) free, so this shouldn't be a free resource
issue. it seems to only occur if i try to rapidly open and close the
device (when i say 'rapidly' i mean about once per second for about
10-25 seconds).
it's sub-ideal, but i'm using esd for now (with a really high timeout
for releasing the pcm device) to avoid the excessive reopening behaviour.
thanks for your help - please let me know of any other ways i can try to
gather information.
-brian
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-02-07 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E40BA0F.9070600@ece.cornell.edu>
2003-02-07 11:56 ` [Alsa-user] sb live dma buffer alloc failure? Takashi Iwai
2003-02-07 19:46 ` Brian J. Tarricone [this message]
2003-02-08 17:10 ` laurent.ml
2003-02-10 12:09 ` Takashi Iwai
2003-02-12 23:00 ` Brian J. Tarricone
2003-02-13 8:56 ` Takashi Iwai
[not found] ` <wazza.87d6m6he5z.fsf@message.id>
2003-02-07 11:58 ` 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=3E440D06.8090803@ece.cornell.edu \
--to=bjt23@ece.cornell.edu \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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