Message-ID: <416C4173.3060408@nortelnetworks.com>
Date: Tue, 12 Oct 2004 14:41:23 -0600
From: Chris Friesen <cfriesen@nortelnetworks.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: Chris Wright <chrisw@osdl.org>
CC: Andries Brouwer <aebr@win.tue.nl>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       wli@holomorphy.com
Subject: Re: [BUG]  oom killer not triggering in 2.6.9-rc3  -- FIXED in -rc4
References: <41672D4A.4090200@nortelnetworks.com> <1097503078.31290.23.camel@localhost.localdomain> <416B6594.5080002@nortelnetworks.com> <20041012094439.GA3223@pclin040.win.tue.nl> <416BF927.7000000@nortelnetworks.com> <20041012130859.G2441@build.pdx.osdl.net>
In-Reply-To: <20041012130859.G2441@build.pdx.osdl.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 842
Lines: 25

Chris Wright wrote:

> Chris, did you try the patch I sent you (it's in mainline now, so if you
> re-test on 2.6.9-rc4 you'd pick it up)?  

Oops.  No I didn't--meant to, but then forgot.  I should have, it seems to be 
fixed in -rc4.

 > With that patch, with 2G of
> memory and no swap, my machine did not lock up, and the conditions that
> the patch protect against were triggered.  And, with the patch backed
> out, kswapd spins out of control.  I believe this is fixed.

2.6.9-rc4 seems sane again.  Start up two memory hogs, one gets killed immediately.

Sweet.

Thanks for your help,

Chris
-
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/