LKML Archive on
help / color / mirror / Atom feed
From: Chris Stromsoe <>
To: Dave Kleikamp <>
Cc: linux-kernel <>,
	Marcelo Tosatti <>
Subject: Re: oops, 2.4.26 and jfs
Date: Fri, 28 May 2004 19:32:51 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, 28 May 2004, Chris Stromsoe wrote:

> 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.
> 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.

Looking back through my mail logs, I've had (and reported) problems with
0-order allocations failing and random hangs with this same workload on 2
other machines at least as far back as early April 3, 2004, with 2.4.23.
See <>
for an earlier report.

Differences between then and now:  I'm using tmpfs instead of rd,
CONFIG_HIGHIO=y is set, and I've upgraded the kernel to 2.4.26.


  reply	other threads:[~2004-05-29  2:33 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 [this message]
2004-05-30 17:38     ` Marcelo Tosatti
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 \ \ \ \ \ \

* 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).