From: J M Cerqueira Esteves <jmce@artenumerica.com>
To: linux-kernel@vger.kernel.org
Cc: support@artenumerica.com
Subject: oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T
Date: Wed, 01 Mar 2006 17:01:55 +0000 [thread overview]
Message-ID: <4405D383.5070201@artenumerica.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3494 bytes --]
Greetings
On a dual EM64T Xeon with 4GB of RAM, I am getting apparently "innocent"
processes killed by oom-killer with gfp_mask=0xd1 (with all or almost
all swap space still available).
This happens when running a couple of Gaussian and other computational
chemistry software processes each using ~ 800MB-1GB of RAM. Sometimes
oom-killer kills one or two of those processes, with the kernel messages
shown below. Unfortunately I don't have a simpler recipe to induce this
behavior... (it may even be triggered only by some Gaussian runs with a
particular set of input parameters; it doesn't happen always).
I haven't tried 2.6.15 kernels yet, but according to recent reports in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175173
even those may still have oom-killer problems (like this?).
Since I'm not yet familiar with the meaning of much of the data output
in the following kernel messages, could someone suggest some appropriate
course of action to troubleshoot this? Any recommended kernel
versions/patches/settings?
oom-killer: gfp_mask=0xd1
DMA per-cpu:
cpu 0 hot: low 2, high 6, batch 1
cpu 0 cold: low 0, high 2, batch 1
cpu 1 hot: low 2, high 6, batch 1
cpu 1 cold: low 0, high 2, batch 1
cpu 2 hot: low 2, high 6, batch 1
cpu 2 cold: low 0, high 2, batch 1
cpu 3 hot: low 2, high 6, batch 1
cpu 3 cold: low 0, high 2, batch 1
Normal per-cpu:
cpu 0 hot: low 62, high 186, batch 31
cpu 0 cold: low 0, high 62, batch 31
cpu 1 hot: low 62, high 186, batch 31
cpu 1 cold: low 0, high 62, batch 31
cpu 2 hot: low 62, high 186, batch 31
cpu 2 cold: low 0, high 62, batch 31
cpu 3 hot: low 62, high 186, batch 31
cpu 3 cold: low 0, high 62, batch 31
HighMem per-cpu: empty
Free pages: 13436kB (0kB HighMem)
Active:396041 inactive:586624 dirty:180807 writeback:0 unstable:0
free:3359 slab:22149 mapped:256439 pagetables:1997
DMA free:24kB min:28kB low:32kB high:40kB active:0kB inactive:0kB
present:16384kB pages_scanned:2 all_unreclaimable? yes
lowmem_reserve[]: 0 4848 4848
Normal free:13412kB min:8892kB low:11112kB high:13336kB active:1584168kB
inactive:2346492kB present:4964352kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
HighMem free:0kB min:128kB low:160kB high:192kB active:0kB inactive:0kB
present:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
DMA: 0*4kB 1*8kB 1*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB
0*2048kB 0*4096kB = 24kB
Normal: 1*4kB 4*8kB 6*16kB 113*32kB 1*64kB 5*128kB 3*256kB 0*512kB
0*1024kB 0*2048kB 2*4096kB = 13412kB
HighMem: empty
Swap cache: add 10, delete 10, find 3/6, race 0+0
Free swap = 7036300kB
Total swap = 7036304kB
Out of Memory: Killed process 9308 (l804.exe).
I also got similar messages running the same software
after setting /proc/sys/vm/overcommit_memory as "2".
Some machine details:
Tyan Tiger i7525 (S2672) motherboard;
2 Intel Xeon 3.2 GHz CPUs (2MB cache each);
4GB of ECC RAM;
Radeon X300 VGA card.
This is running Ubuntu 5.10 (Breezy) for x8_64 systems, with a 2.6.12
kernel (Ubuntu linux-source-2.6.12-10.28) recompiled
with small configuration differences from the default Ubuntu one
(no K8 NUMA, processor family Intel EM64T, SMP support,
CONFIG_SCHED_SMT, some unneeded hardware support suppressed, ...).
Feel free to request any additional data which could be helpful (kernel
configuration. hardware details, ...).
Best regards and thanks in advance
J Esteves
--
+351 939838775 Skype:jmcerqueira http://del.icio.us/jmce
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2006-03-01 17:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 17:01 J M Cerqueira Esteves [this message]
2006-03-02 9:17 ` oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T Andrew Morton
2006-03-03 15:50 ` J M Cerqueira Esteves
2006-03-04 15:57 ` oom-killer: gfp_mask=0xd1 with 2.6.15.4 on EM64T [previously 2.6.12] J M Cerqueira Esteves
2006-03-05 0:15 ` Andrew Morton
2006-03-05 2:55 ` J M Cerqueira Esteves
2006-03-05 10:07 ` J M Cerqueira Esteves
2006-03-06 8:47 ` J M Cerqueira Esteves
2006-03-06 9:02 ` Andrew Morton
2006-03-06 18:03 ` Jun'ichi Nomura
2006-03-17 9:47 ` J M Cerqueira Esteves
2006-03-06 9:19 ` J M Cerqueira Esteves
2006-03-06 9:28 ` Andrew Morton
2006-03-06 10:45 ` J M Cerqueira Esteves
2006-03-06 15:56 ` Randy.Dunlap
2006-03-05 0:12 ` oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T Andrew Morton
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=4405D383.5070201@artenumerica.com \
--to=jmce@artenumerica.com \
--cc=linux-kernel@vger.kernel.org \
--cc=support@artenumerica.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox