mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: riel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4.23-pre VM regression?
Date: Thu, 16 Oct 2003 15:24:12 +0200	[thread overview]
Message-ID: <20031016132412.GB1348@velociraptor.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0310160949230.2388-100000@logos.cnet>

On Thu, Oct 16, 2003 at 09:52:30AM -0200, Marcelo Tosatti wrote:
> 
> Andrea, 
> 
> Martin first reported problems with "gzip -dc file | less" (280MB file).
> less was getting killed. He had no swap... I asked him to add some swap
> and it works now. Fine. 
> 
> The thing is that with 2.4.22 less was being killed, but with 2.4.23-pre
> he gets:

note, that's a true oom, less needs to allocate 280MB and it doesn't fit
in ram. there's no bug as far as I can tell.

a `vmstat 1` could confirm that.

> >> And yes, the app was killed:
> > >
> > > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> > > VM: killing process named
> > > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> > > VM: killing process gpm
> > > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> > > VM: killing process sendmail
> > > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> > > VM: killing process less

here the vm keeps killing until 'less' - the real offender - is nuked.

> So a lot of processes which should not get killed are dying. This is
> really bad. I was afraid it could happen and it did.
> 
> What now? Resurrect OOM-killer? 

the oom killer has the problem I outlined some email ago, with shared
memory it gets fooled badly etc.., though in a desktop with all tiny
tasks except the memory-hog (`less` in this case) it works well.

> 
> > > Hi,
> > >   it's a long time I haven't seen sthis messages, but it just happened that
> > > I did on my laptop ASUS L3880C(1GB RAM). The message show on
> > > 2.4.23-pre5+acpi20030918 and 2.4.23-pre7. The application get's killed on
> > > 2.4.22-acpi20030918 too, just without the "0-order allocation" message.
> > > I enabled in kernel the VM allocation debug option when configuring, but
> > > apparently I have to turn it on also somewhere else. *Documentation* is
> > > missing: 1) the help in "make config/menuconfig" etc. doesn't say anything,
> > > the Documentation subdirectory doesn't say anything except "debug" as
> > > kernel boot option on command-line(I did that too, but no change) and also
> > > linux kernel-FAQ doesn't say either. :(
> > >
> > > How I tested?
> > > `gzip -dc file | less' and pressed `G' to jump to the very end of the file.
> > > The filesize is 280MB only. In a while, the mouse stopps moving for a
> > > while, than the system gets sometimes unloaded, fan is raises it's RPM's up
> > > and down town to time, and mouse cursor eventually does a move and then
> > > less command gets killed. In dmesg I found:
> > >
> > > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
> > > VM: killing process less

this time it was killed immediatly even with the new changes.

> 
> With 2.4.22:
> 
> > 2.4.22-acpi-20030918 with HIGHMEM gives only in dmesg:
> >
> > Out of Memory: Killed process 1904 (less).

same here obviously.

Andrea - If you prefer relying on open source software, check these links:
	    rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/
	    http://www.cobite.com/cvsps/

  parent reply	other threads:[~2003-10-16 13:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16 11:52 Marcelo Tosatti
2003-10-16 13:15 ` Tvrtko A. Uršulin
2003-10-16 13:24 ` Andrea Arcangeli [this message]
2003-10-16 12:29   ` Marcelo Tosatti
2003-10-16 13:35     ` Andrea Arcangeli
2003-10-19 23:21       ` Ken Moffat
2003-10-21  9:25         ` Stephan von Krawczynski
2003-10-27 21:11           ` Mike Fedyk
     [not found] <fa.jkt135h.1l0s0t@ifi.uio.no>
     [not found] ` <fa.j3l9liv.1djudhj@ifi.uio.no>
2003-10-16 23:37   ` Andreas Hartmann
2003-10-18 22:09 A.D.F.

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=20031016132412.GB1348@velociraptor.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=riel@redhat.com \
    /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®