Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965373AbXATVDp (ORCPT ); Sat, 20 Jan 2007 16:03:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965384AbXATVDp (ORCPT ); Sat, 20 Jan 2007 16:03:45 -0500 Received: from lucidpixels.com ([66.45.37.187]:42865 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965373AbXATVDo (ORCPT ); Sat, 20 Jan 2007 16:03:44 -0500 Date: Sat, 20 Jan 2007 16:03:42 -0500 (EST) From: Justin Piszcz X-X-Sender: jpiszcz@p34.internal.lan To: Avuton Olrich 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 In-Reply-To: <3aa654a40701201245s72b2f76hc70ddd94b70ba99c@mail.gmail.com> Message-ID: References: <3aa654a40701201245s72b2f76hc70ddd94b70ba99c@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1462 Lines: 41 On Sat, 20 Jan 2007, Avuton Olrich wrote: > On 1/20/07, Justin Piszcz 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/