> 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@xxxxxxxxxxxxxxx > > 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. > > - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
