| To: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2 |
| From: | Pavel Machek <pavel@xxxxxx> |
| Date: | Thu, 25 Jan 2007 01:32:42 +0100 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.64.0701241837550.2930@xxxxxxxxxxxxxxxx> |
| References: | <Pine.LNX.4.64.0701211424170.2552@xxxxxxxxxxxxxxxx> <20070122133735.GB4493@xxxxxx> <Pine.LNX.4.64.0701221348020.11525@xxxxxxxxxxxxxxxx> <Pine.LNX.4.64.0701241837550.2930@xxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.11+cvs20060126 |
Hi!
> > 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!
Okay, so try mem=700M or disable CONFIG_HIGHMEM or something.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
|
| Previous by Date: | Re: [PATCH 1/2]: Fix BUG in cancel_dirty_pages on XFS, Nick Piggin |
|---|---|
| Next by Date: | Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2, Justin Piszcz |
| Previous by Thread: | Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2, Justin Piszcz |
| Next by Thread: | Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2, Justin Piszcz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |