LKML Archive on
help / color / mirror / Atom feed
From: Marcelo Tosatti <>
To: Chris Stromsoe <>
Cc: Dave Kleikamp <>,
	linux-kernel <>
Subject: Re: oops, 2.4.26 and jfs
Date: Sun, 30 May 2004 14:38:58 -0300	[thread overview]
Message-ID: <20040530173858.GA11692@logos.cnet> (raw)
In-Reply-To: <>

 On Fri, May 28, 2004 at 06:16:22PM -0700, Chris Stromsoe wrote:
> On Fri, 28 May 2004, Dave Kleikamp wrote:
> > On Fri, 2004-05-28 at 15:15, Chris Stromsoe wrote:
> > > This morning during a cron run while doing a find across /, I got the
> > > following oops.
> >
> > The oops is fixed in 2.4.27-pre3 with the patch:
> >
> >
> > jfs still may give you problems if 0-order allocations are failing, but
> > it's not supposed to trap.
> Thanks, patch applied.
> Aside from that:
> > May 26 06:28:10 begonia kernel: __alloc_pages: 0-order allocation failed
> > (gfp=0x1f0/0)
> I'm curious about why 0-order allocations would fail.  From everything
> I've read (google searching for the error message), that indicates an out
> of memory condition, which shouldn't be the case.
> The box in question has 4Gb of physical ram (512Mb is used as tmpfs) and
> 9Gb of swap.  When the oops happened, no swap was in use.  Physical ram
> was pretty much filled, but no swap at all.  OOM_KILLER is not enabled.

Hi Chris, 

This seems to be a normal allocation (which can wait), it really
looks the system was out of memory. 

Can you stick a call to show_free_areas() in mm/page_alloc.c after 

        printk(KERN_NOTICE "__alloc_pages: %u-order allocation failed (gfp=0x%x/%i)\n",
               order, gfp_mask, !!(current->flags & PF_MEMALLOC));

so we know the state of the memory areas when it happens again.

Also turn on /proc/sys/vm/vm_gfp_debug.

> There's nothing especially exotic in the box.  It does a lot of network
> traffic (eepro100) and a lot of disk traffic (aic7xxx).  The morning cron
> jobs had just kicked off.  Two of them do "find /"  -- I believe that the
> second one was running when it happened.

  parent reply	other threads:[~2004-05-30 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 20:15 oops, 2.4.26 and jfs Chris Stromsoe
2004-05-28 20:31 ` Dave Kleikamp
2004-05-29  1:16   ` Chris Stromsoe
2004-05-29  2:32     ` Chris Stromsoe
2004-05-30 17:38     ` Marcelo Tosatti [this message]
2004-05-31 11:19       ` Chris Stromsoe
2004-05-31 14:05         ` Marcelo Tosatti

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040530173858.GA11692@logos.cnet \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).