mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Jens Axboe <axboe@suse.de>
Cc: Andries Brouwer <aebr@win.tue.nl>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: oom killer gone nuts
Date: Fri, 21 Jan 2005 09:41:11 +0100	[thread overview]
Message-ID: <20050121084111.GB7703@dualathlon.random> (raw)
In-Reply-To: <20050121080940.GA2763@suse.de>

On Fri, Jan 21, 2005 at 09:09:41AM +0100, Jens Axboe wrote:
> Jan 20 13:22:15 wiggum kernel: oom-killer: gfp_mask=0xd1

This was a GFP_KERNEL|GFP_DMA allocation triggering this. However it
didn't look so much out of DMA zone, there's 4M of ram free. Could be
the ram was relased by another CPU in the meantime if this was SMP (or
even by an interrupt in UP too).

Could very well be you'll get things fixed by the lowmem_reserve patch,
that will reserve part of the dma zone, so with it you're sure it
couldn't have gone below 4M due slab allocs like skb.

I recommend trying again with the patches applied, the oom stuff is so
buggy right now that it's better you apply the fixes and try again, and
if it still happens we know it's a regression.

Thanks!

  reply	other threads:[~2005-01-21  8:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 12:34 Jens Axboe
2005-01-20 13:15 ` Andries Brouwer
2005-01-20 14:00   ` Marcelo Tosatti
2005-01-20 18:15     ` Andries Brouwer
2005-01-20 17:15   ` Andrea Arcangeli
2005-01-20 20:52     ` Andries Brouwer
2005-01-20 21:57       ` Chris Friesen
2005-01-20 23:27         ` Andrea Arcangeli
2005-01-21  7:42     ` Jens Axboe
2005-01-21  8:05       ` Andrea Arcangeli
2005-01-21  8:09         ` Jens Axboe
2005-01-21  8:41           ` Andrea Arcangeli [this message]
2005-01-21  8:46             ` Jens Axboe

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=20050121084111.GB7703@dualathlon.random \
    --to=andrea@suse.de \
    --cc=aebr@win.tue.nl \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®