From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Brian J. Tarricone" Subject: Re: [Alsa-user] sb live dma buffer alloc failure? Date: Fri, 07 Feb 2003 14:46:14 -0500 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <3E440D06.8090803@ece.cornell.edu> References: <3E40BA0F.9070600@ece.cornell.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Takashi Iwai Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org 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