From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Re: [Alsa-user] sb live dma buffer alloc failure? Date: Mon, 10 Feb 2003 13:09:50 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <3E40BA0F.9070600@ece.cornell.edu> <3E440D06.8090803@ece.cornell.edu> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: laurent.ml@linuxfr.org Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Sat, 08 Feb 2003 17:10:02 +0000, laurent.ml@linuxfr.org wrote: > > "Brian J. Tarricone" writes: > > whereas the xmms(alsa drv) loop gave: > ALSA lib pcm_hw.c:297:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Cannot allocate memory > 2.4.21pre4 don't produce kernel error, whereas 2.4.21pre4aa1 gives > "kernel: __alloc_pages: 0-order allocation failed (gfp=0x21/0)" kind of error. it's weird. the gfp mask has no GFP_WAIT bit. could you check which call triggers this? or did it come from 0.9.0rc6 driver? then i understand the reason... > After the xmms(alsa output) problem, I was able to rmmod alsa modules, then > reload them. the new code on cvs will do pre-allocation, so this problem should no longer appear, anyway. Takashi ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com