LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	xfs@oss.sgi.com
Subject: Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
Date: Wed, 24 Jan 2007 18:39:07 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701241837550.2930@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0701221348020.11525@p34.internal.lan>

> Is it highmem-related? Can you try it with mem=256M?

Bad idea, the kernel crashes & burns when I use mem=256, I had to boot 
2.6.20-rc5-6 single to get back into my machine, very nasty.  Remember I 
use an onboard graphics controller that has 128MB of RAM allocated to it 
and I believe the ICH8 chipset also uses some memory, in any event mem=256 
causes the machine to lockup before it can even get to the boot/init 
processes, the two leds on the keyboard were blinking, caps lock and 
scroll lock and I saw no console at all!

Justin.

On Mon, 22 Jan 2007, Justin Piszcz wrote:

> 
> 
> On Mon, 22 Jan 2007, Pavel Machek wrote:
> 
> > On Sun 2007-01-21 14:27:34, Justin Piszcz wrote:
> > > Why does copying an 18GB on a 74GB raptor raid1 cause the kernel to invoke 
> > > the OOM killer and kill all of my processes?
> > > 
> > > Doing this on a single disk 2.6.19.2 is OK, no issues.  However, this 
> > > happens every time!
> > > 
> > > Anything to try?  Any other output needed?  Can someone shed some light on 
> > > this situation?
> > 
> > Is it highmem-related? Can you try it with mem=256M?
> > 
> > 							Pavel
> > -- 
> > (english) http://www.livejournal.com/~pavelmachek
> > (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> 
> I will give this a try later or tomorrow, I cannot have my machine crash 
> at the moment.
> 
> Also, the onboard video on the Intel 965 chipset uses 128MB, not sure if 
> that has anything to do with it because after the system kill -9's all the 
> processes etc, my terminal looks like garbage.
> 
> Justin.
> 
> 

  parent reply	other threads:[~2007-01-24 23:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21 19:27 Justin Piszcz
2007-01-22 13:37 ` Pavel Machek
2007-01-22 18:48   ` Justin Piszcz
2007-01-22 23:47     ` Pavel Machek
2007-01-24 23:39     ` Justin Piszcz [this message]
2007-01-24 23:42       ` Justin Piszcz
2007-01-25  0:32       ` Pavel Machek
2007-01-25  0:36         ` Justin Piszcz
2007-01-25  0:58         ` Justin Piszcz
2007-01-25  9:08         ` Justin Piszcz
2007-01-25 22:34           ` Mark Hahn
2007-01-26  0:22             ` Justin Piszcz
2007-01-22 19:57 ` Andrew Morton
2007-01-22 20:20   ` Justin Piszcz
2007-01-23  0:37   ` Donald Douwsma
2007-01-23  1:12     ` Andrew Morton
2007-01-24 23:40   ` Justin Piszcz
2007-01-25  0:10   ` Justin Piszcz
2007-01-25  0:36     ` Nick Piggin
2007-01-25 11:11       ` Justin Piszcz
2007-01-25  1:21     ` Bill Cizek
2007-01-25 11:13       ` Justin Piszcz
2007-01-25  0:34   ` 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.0701241837550.2930@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=xfs@oss.sgi.com \
    --subject='Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2' \
    /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

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