All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: holborn@telefonica.net
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: sfxload / asfxload page allocation failure
Date: Tue, 13 Apr 2004 17:27:37 +0200	[thread overview]
Message-ID: <s5hisg3vqxi.wl@alsa2.suse.de> (raw)
In-Reply-To: <200404131237.11198.holborn@telefonica.net>

At Tue, 13 Apr 2004 12:37:10 +0100,
holborn wrote:
> 
> 
> Hi!
> 
> I have problems when i try to load "big" soundfonts, in older versions i was 
> load this soundfonts without probems.
> 
> when i run sfxload or asfxload with PC51f.sf2 (for example ... ) asfxload or 
> sfxload try to load but no returnd to command line. No way to kill the 
> process, no way to load other soundfonts and when i reboot i have this 
> message:

well, it means that your machine has really no RAM available for the
soundfont.  on 2.4 kernel (or older ALSA version), the driver
allocated the pages in atomic, so it doesn't go to sleep.
on 2.6 and current ALSA, the page allocation is done with GFP_KERNEL,
so it may sleep until the page is available.  it can take a long time
but must not be infinitely long.

could you check whether the "page allocation failure" message already
appeared when sfxload hangs up?
does the message appears once or many times?


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-04-13 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 11:37 sfxload / asfxload page allocation failure holborn
2004-04-13 15:27 ` Takashi Iwai [this message]
2004-04-13 16:22   ` holborn
2004-04-13 17:00     ` Takashi Iwai
2004-04-14  1:25       ` holborn

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=s5hisg3vqxi.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=holborn@telefonica.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 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.