From: Chris Friesen <cfriesen@nortelnetworks.com>
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
Date: Tue, 12 Oct 2004 14:41:23 -0600 [thread overview]
Message-ID: <416C4173.3060408@nortelnetworks.com> (raw)
In-Reply-To: <20041012130859.G2441@build.pdx.osdl.net>
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
next prev parent reply other threads:[~2004-10-12 20:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 0:14 [BUG] oom killer not triggering in 2.6.9-rc3 Chris Friesen
2004-10-09 0:26 ` Chris Wright
2004-10-11 13:58 ` Alan Cox
2004-10-12 5:03 ` Chris Friesen
2004-10-12 5:22 ` William Lee Irwin III
2004-10-12 15:24 ` Chris Friesen
2004-10-12 16:28 ` William Lee Irwin III
2004-10-12 9:44 ` Andries Brouwer
2004-10-12 15:32 ` Chris Friesen
2004-10-12 20:08 ` Chris Wright
2004-10-12 20:41 ` Chris Friesen [this message]
2004-10-12 20:54 ` [BUG] oom killer not triggering in 2.6.9-rc3 -- FIXED in -rc4 Chris Wright
2004-10-12 21:02 ` [BUG] oom killer not triggering in 2.6.9-rc3 Alan Cox
2004-10-12 22:25 ` Chris Friesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416C4173.3060408@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=aebr@win.tue.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.