linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Andrew Kay <Andrew.J.Kay@syntegra.com>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>, linux-mm@kvack.org
Subject: Re: kernel: __alloc_pages: 1-order allocation failed
Date: Wed, 29 Aug 2001 17:13:59 +0200	[thread overview]
Message-ID: <20010829150716Z16100-32383+2280@humbolt.nl.linux.org> (raw)
In-Reply-To: <3B8CF2BA.5030506@syntegra.com>

On August 29, 2001 03:48 pm, Andrew Kay wrote:
> Here's some 'cut' output from /var/log/messages.  There is a lot more 
> from where this came from.  Some of it looks a bit different, I included 
> it below the first 3 errors.  I can post the 165k gzipped messages file 
> somewhere if someone wants to look at the whole thing.
> 
> __alloc_pages: 1-order allocation failed (gfp=0x20/0).
> Call Trace: [<c012db70>] [<c012de1e>] [<c012a69e>] [<c012aa21>] 
> [<c0211032>]
>     [<c02392da>] [<c023669f>] [<c02355c1>] [<c02399a1>] [<c01b000f>] 
> [<c011c9bc>]
>     [<c01b000f>] [<c02158e6>] [<c021a714>] [<c02158e6>] [<c022173d>] 
> [<c0221638>]
>     [<c0221b5d>] [<c0211f53>] [<c0221638>] [<c023099a>] [<c0211f53>] 
> [<c0211f68>]
>     [<c02120b9>] [<c023698e>] [<c0236c65>] [<c023711d>] [<c021f07f>] 
> [<c021f40a>]
>     [<c01b0571>] [<c0215fae>] [<c0119533>] [<c0108785>] [<c0105230>] 
> [<c0105230>]
>     [<c0106e34>] [<c0105230>] [<c0105230>] [<c010525c>] [<c01052c2>] 
> [<c0105000>]
>     [<c010505f>]
> [similar]
>
> Daniel Phillips wrote:
> > On August 28, 2001 12:28 am, Marcelo Tosatti wrote:
> > 
> >>On Tue, 28 Aug 2001, Daniel Phillips wrote:
> >>
> >>>On August 27, 2001 10:14 pm, Andrew Kay wrote:
> >>>
> >>>>I am having some rather serious problems with the memory management (i 
> >>>>think) in the 2.4.x kernels.  I am currently on the 2.4.9 and get lots 
> >>>>of these errors in /var/log/messages.
> >>>>
> >>Its probably the bounce buffering thingie.
> >>
> >>I'll send a patch to Linus soon.
> >>
> > 
> > That's what I thought too, but I thought, why not give him the patch and be 
> > sure.

OK, it's not a bounce buffer because the allocation isn't __GFP_WAIT (0x10).
It's GFP_ATOMIC and there are several hundred of those throughout the kernel so
I'm not going to try to guess which one.  Could you please pass a few of your
backtraces through ksymoops make them meaningful?

--
Daniel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2001-08-29 15:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 20:14 Andrew Kay
2001-08-27 22:57 ` Daniel Phillips
2001-08-27 22:28   ` Marcelo Tosatti
2001-08-28  0:08     ` Daniel Phillips
2001-08-29 13:48       ` Andrew Kay
2001-08-29 15:13         ` Daniel Phillips [this message]
2001-08-29 16:14           ` Andrew Kay
2001-08-29 18:00             ` Daniel Phillips
2001-08-30 14:24               ` Andrew Kay
2001-08-30 22:19                 ` Daniel Phillips
2001-08-30 22:39                   ` Andrew Kay
2001-08-30 23:04                     ` Daniel Phillips
2001-08-31 13:44                       ` Andrew Kay
2001-08-28  6:27     ` Roger Larsson

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=20010829150716Z16100-32383+2280@humbolt.nl.linux.org \
    --to=phillips@bonn-fries.net \
    --cc=Andrew.J.Kay@syntegra.com \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    /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