All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: laurent.ml@linuxfr.org
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: [Alsa-user] sb live dma buffer alloc failure?
Date: Mon, 10 Feb 2003 13:09:50 +0100	[thread overview]
Message-ID: <s5h1y2g49rl.wl@alsa2.suse.de> (raw)
In-Reply-To: <wazza.87znp6pul1.fsf@message.id>

At Sat, 08 Feb 2003 17:10:02 +0000,
laurent.ml@linuxfr.org wrote:
> 
> "Brian J. Tarricone" <bjt23@ece.cornell.edu> 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

  reply	other threads:[~2003-02-10 12:09 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
2003-02-08 17:10     ` laurent.ml
2003-02-10 12:09       ` Takashi Iwai [this message]
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=s5h1y2g49rl.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=laurent.ml@linuxfr.org \
    /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.