Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751029AbXAUQsK (ORCPT ); Sun, 21 Jan 2007 11:48:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751038AbXAUQsJ (ORCPT ); Sun, 21 Jan 2007 11:48:09 -0500 Received: from lucidpixels.com ([66.45.37.187]:35725 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751019AbXAUQsI (ORCPT ); Sun, 21 Jan 2007 11:48:08 -0500 Date: Sun, 21 Jan 2007 11:48:07 -0500 (EST) From: Justin Piszcz X-X-Sender: jpiszcz@p34.internal.lan To: thunder7@xs4all.nl cc: Avuton Olrich , 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: <20070121155219.GA7413@amd64.of.nowhere> Message-ID: References: <3aa654a40701201245s72b2f76hc70ddd94b70ba99c@mail.gmail.com> <20070121155219.GA7413@amd64.of.nowhere> 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: 1380 Lines: 40 On Sun, 21 Jan 2007, thunder7@xs4all.nl wrote: > From: Justin Piszcz > Date: Sat, Jan 20, 2007 at 04:03:42PM -0500 > > > > > > 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 :( > > > Well, if you can't go back, you could always test 2.6.20-rc5. That's why > it's out there :-) It can't be any worse! > > Good luck, > Jurriaan > -- > It might look like I'm doing nothing, but at the cellular level I'm really > quite busy. > Hans Haas > Debian (Unstable) GNU/Linux 2.6.20-rc5 2x2011 bogomips load 1.97 > the Jack Vance Integral Edition: http://www.integralarchive.org > The HDD temp bug -- OK, nice. What about all of the changes with NAT? I see that it operates on level-3/network wise, I enabled that and backward compatiblity support as well, but when my iptables rules kick in, it says no such driver/etc for `nat'-- is there a new target for iptables now or did I miss a kernel option? 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/