All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Ville Herva <vherva@niksula.cs.hut.fi>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	linux-kernel@vger.kernel.org
Subject: Re: lot of VM problem with 2.4.23
Date: Mon, 22 Dec 2003 20:09:43 +0100	[thread overview]
Message-ID: <20031222190943.GF18767@dualathlon.random> (raw)
In-Reply-To: <20031222070344.GL1524@niksula.cs.hut.fi>

On Mon, Dec 22, 2003 at 09:03:44AM +0200, Ville Herva wrote:
> On Sun, Dec 21, 2003 at 11:23:38PM +0100, you [Willy Tarreau] wrote:
> > >
> > > Dec 21 22:08:44 stock kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> > > Dec 21 22:08:44 stock kernel: OOM: nr_swap_pages=0cd865e6c c012e1e8 c0262e3c 00000000 000001d2 00000000 00000001 cd863c00 
> > 
> > OK, so there's no available swap anymore (nr_swap_pages=0, Marcelo forgot the
> > '\n' in the patch). I simply think that with other kernels, you're very short
> > of memory, but it runs, while with this one, all memory gets consumed, and
> > since there's no smart oom killer, one process has to get killed.
> 
> BTW, I have a box with 128MB ram and 512MB swap running 2.4.21-jam1 (it has
> the -aa vm). I can't shut it down cleanly, because trying it goes into
> endless loop trying to free memory when turning off swap. Nothing but
> alt-sysrq-b seems to work.
> 
> I don't know if there is a kernel memory leak, since all user level
> processes should be killed at that point, right? Unfortunately I didn't have
> time to dig deeper, as the box is in (sort of) production.

if this is a leak, I doubt it has been introduced recently, the only
swap accounting related change was in the shm layer, and it was supposed
to be a race fix. You may want to check if you've some shm allocated
in /dev/shm or ipcs, while the machine reboots.

  parent reply	other threads:[~2003-12-22 19:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21  0:14 lot of VM problem with 2.4.23 Octave
2003-12-21  9:30 ` Peter Zaitsev
2003-12-21 14:37   ` Marcelo Tosatti
2003-12-21 15:03     ` Octave
2003-12-21 15:42       ` Willy Tarreau
2003-12-21 16:13         ` Octave
2003-12-21 18:45           ` Marcelo Tosatti
2003-12-21 19:14             ` Octave
2003-12-21 20:45               ` Marcelo Tosatti
2003-12-21 21:09                 ` Octave
2003-12-21 22:23                   ` Willy Tarreau
2003-12-22  7:03                     ` Ville Herva
2003-12-22 18:35                       ` Mike Fedyk
2003-12-22 21:12                         ` Ville Herva
2003-12-22 22:52                           ` Gene Heskett
2003-12-23  8:51                             ` Ville Herva
2003-12-22 19:09                       ` Andrea Arcangeli [this message]
2003-12-22 21:18                         ` Ville Herva
2003-12-21 18:47     ` Octave
2003-12-21 18:59       ` Tomas Szepe
2003-12-21 23:43         ` Octave
2003-12-22 11:27           ` Marcelo Tosatti
2003-12-22 12:30             ` Octave
2003-12-22 15:17               ` Andrea Arcangeli
2003-12-23 22:59                 ` Octave
2003-12-21 10:43 ` bert hubert
     [not found] <14ZDV-1H1-1@gated-at.bofh.it>
2003-12-21 13:53 ` Kristian

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=20031222190943.GF18767@dualathlon.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=vherva@niksula.cs.hut.fi \
    /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.