From: Christoph Lameter <cl@linux-foundation.org>
To: Marco Nietz <m.nietz-mm@iplabs.de>
Cc: linux-mm@kvack.org
Subject: Re: oom-killer why ?
Date: Mon, 25 Aug 2008 13:55:45 -0500 [thread overview]
Message-ID: <48B30031.201@linux-foundation.org> (raw)
In-Reply-To: <48B2EB37.2000200@iplabs.de>
Marco Nietz wrote:
> It's should be possible to reproduce the oom, but it's a Production Server.
>
> The oom happens after if've increased the Maximum Connections and
> Shared-Buffers for the Postgres Database Server on that Machine.
>
> It's kernel: 2.6.18-6-686-bigmem a Debian Etch Server.
Hmmm... That should be fairly stable. I wonder how prostgres handles the
buffers? If the pages are mlocked and are required to be in lowmem then what
you saw could be related to the postgres configuration.
> And here is the Complete dmesg:
The problem is that the boot messages are cut off we cannot see the basic
operating system configuration and the hardware that was detected.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-08-25 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 11:25 oom-killer why ? Marco Nietz
2008-08-25 15:56 ` Christoph Lameter
2008-08-25 16:18 ` Marco Nietz
2008-08-25 16:29 ` Christoph Lameter
2008-08-25 17:26 ` Marco Nietz
2008-08-25 18:55 ` Christoph Lameter [this message]
2008-08-26 6:44 ` Marco Nietz
2008-08-26 13:23 ` Christoph Lameter
2008-08-26 10:45 ` Larry Woodman
2008-08-25 17:36 ` Larry Woodman
2008-08-26 11:11 ` Balbir Singh
2008-08-26 12:00 ` Marco Nietz
2008-08-26 13:15 ` Balbir Singh
2008-08-26 13:18 ` Balbir Singh
2008-08-26 19:09 ` Larry Woodman
2008-08-27 2:32 ` Balbir Singh
2008-08-27 6:21 ` Marco Nietz
2008-08-30 18:19 ` Rik van Riel
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=48B30031.201@linux-foundation.org \
--to=cl@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=m.nietz-mm@iplabs.de \
/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.