From: Nico Schottelius <nico-kernel-20071219@schottelius.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Out of memory and no killable processes: 2.6.22-2-686-bigmem
Date: Wed, 19 Dec 2007 06:55:50 +0100 [thread overview]
Message-ID: <20071219055550.GE21042@denkbrett.schottelius.org> (raw)
In-Reply-To: <4768692A.3030204@shaw.ca>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
Hello Robert,
Robert Hancock [Tue, Dec 18, 2007 at 06:43:22PM -0600]:
> How much RAM is in these machines?
8 GiB
> If you're running tons of memory, it
> really is better to run a 64-bit kernel if possible.
Sure? Afaik that results in a bit slower access to memory and appart
from being able to address MUCH more memory doesn't change the
situation.
Perhaps I missed something.
And updating to 64 Bit kernel also implies changing the userland, so
a reinstall would be necessary, wouldn't it?
> I believe there are
> some cases where low memory can be pretty easily exhausted on machines with
> lots of high memory.
Some minutes ago the third machine of that type freezed.
with 7 GiB of *free* memory, before getting oom+panic.
The thing that looks pretty the same is that the inode table / open
inodes shrinked very heavy from 41k to about 2k before the freeze
in about 3 days.
Same kernel, same Dell 1955 hardware, different machine.
Is it possible to debug this issue somehow?
Nico
--
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-12-19 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.oSel00y9Hn5hvV3laxPiw9blEfU@ifi.uio.no>
2007-12-19 0:43 ` Robert Hancock
2007-12-19 5:55 ` Nico Schottelius [this message]
2007-12-19 8:56 ` Parag Warudkar
2007-12-19 19:14 ` Jiri Slaby
2007-12-19 8:57 ` Jiri Slaby
2007-12-18 23:56 Nico Schottelius
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=20071219055550.GE21042@denkbrett.schottelius.org \
--to=nico-kernel-20071219@schottelius.org \
--cc=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
all inboxes | Powered by JetHome®