mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Avuton Olrich <avuton@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
Date: Sat, 20 Jan 2007 16:24:25 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701201623570.5597@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0701201602570.4910@p34.internal.lan>


On Sat, 20 Jan 2007, Justin Piszcz wrote:

> 
> 
> On Sat, 20 Jan 2007, Avuton Olrich wrote:
> 
> > On 1/20/07, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> > > Perhaps its time to back to a stable (2.6.17.13 kernel)?
> > >
> > > Anyway, when I run a cp 18gb_file 18gb_file.2 on a dual raptor sw raid1
> > > partition, the OOM killer goes into effect and kills almost all my
> > > processes.
> > >
> > > Completely 100% reproducible.
> > >
> > > Does 2.6.19.2 have some of memory allocation bug as well?
> > 
> > I had been seeing something similar (also with 2.6.19.2), but it's not
> > outputting anything to dmesg, so I was waiting for something to happen
> > before I reported it. It's mostly the same thing, but I've only seen
> > it happen when copying something large (2+ GB) over NFS. Interactivity
> > completely goes away and lockups last 10-15 seconds a piece. Then
> > realized I turned the swap off, so I turned it on and didn't lockup
> > any longer.
> > -- 
> > avuton
> > --
> > Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
> > 
> > 
> 
> My swap is on, 2GB ram and 2GB of swap on this machine.  I can't go back 
> to 2.6.17.13 as it does not recognize the NICs in my machine correctly and 
> the Alsa Intel HD Audio driver has bugs etc, I guess I am stuck with 
> 2.6.19.2 :(
> 
> Justin.
> 
> 

The weird part is nothing shows high memory usage in top or via ps, the 
kernel just freaks and kill -9's almost all of my processes.

Nasty VM bug?

Justin.

  reply	other threads:[~2007-01-20 21:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20 20:20 Justin Piszcz
2007-01-20 20:45 ` Avuton Olrich
2007-01-20 21:03   ` Justin Piszcz
2007-01-20 21:24     ` Justin Piszcz [this message]
2007-01-21 15:52     ` thunder7
2007-01-21 15:54       ` Justin Piszcz
2007-01-26 17:49         ` Adrian Bunk
2007-01-26 17:50           ` Justin Piszcz
2007-01-21 16:48       ` Justin Piszcz
2007-01-21 17:02         ` thunder7
2007-01-21 17:08           ` Justin Piszcz
2007-01-21 17:29             ` 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible (multi-threaded USB no go) Justin Piszcz
2007-01-22  6:33               ` Greg KH
2007-01-22 10:56                 ` Justin Piszcz

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=Pine.LNX.4.64.0701201623570.5597@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=avuton@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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®