From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: help interpreting oom-killer output
Date: Tue, 20 Sep 2005 17:53:58 -0600 [thread overview]
Message-ID: <4330A116.1040107@shaw.ca> (raw)
In-Reply-To: <4OY0C-5kE-59@gated-at.bofh.it>
Christopher Friesen wrote:
>
> I'm running a modified 2.6.10 on an x86 uniprocessor system. I keep
> having processes killed by the oom killer at the same place while
> running LTP. The system has gigs of memory, so I find this kind of odd.
>
> Could someone help me interpret the oom-killer output? The first log
> looks like this.
Looks like you were running out of ZONE_NORMAL memory (below 896MB).
There is lots of high memory available but the allocation could not be
satisfied from there.
I would try a newer kernel..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-09-20 23:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4OY0C-5kE-59@gated-at.bofh.it>
2005-09-20 23:53 ` Robert Hancock [this message]
2005-09-21 5:03 ` help interpreting oom-killer output Christopher Friesen
2005-09-20 21:37 Christopher Friesen
2005-09-21 13:37 ` Marcelo Tosatti
2005-09-21 16:07 ` Christopher Friesen
2005-09-21 17:34 ` Christopher 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=4330A116.1040107@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox