From: J M Cerqueira Esteves <jmce@artenumerica.com>
To: linux-kernel@vger.kernel.org
Cc: support@artenumerica.com, Nuno Galamba <ngalamba@fc.ul.pt>
Subject: Re: oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T
Date: Fri, 03 Mar 2006 15:50:01 +0000 [thread overview]
Message-ID: <440865A9.4000102@artenumerica.com> (raw)
In-Reply-To: <20060302011735.55851ca2.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
Andrew Morton wrote:
> That's quite an old kernel. If this is the notorious bio-uses-GFP_DMA bug
> then I'd have expected this kernel to be useless from day one. Did you
> install it recently?
On this double Xeon, yes. I had no problems before with 2.6.12 and the
same "heavy" software on dual Opteron and dual dual core Opteron
machines, and this is my first installation on a EM64T.
At first it seemed everything was ok with 2.6.12 here too, but in a
couple of days we started gettings some of those oom killings when
running some Gaussian jobs. In at least a pair of cases the system froze
completely.
> If you're feeling keen you could add this patch which would confirm it:
Added it and already got output for a similar "killing". Since I'm not
sure what could be most relevant among those messages, I refrained from
attaching them all here, and instead put them at
http://jmce.artenumerica.org/tmp/linux-2.6.12-oom_killings/EM64T-kern.log
> And if it's that bug then I'm afraid you'll have to sit tight until 2.6.16.
> We shouldn't release 2.6.16 until this thing is fixed.
Do those call traces suggest that uncorrected bug you mention?
(And if yes, is there any known way to mitigate the problem? Could it
depend on BIOS settings?)
I'll also be able to try a 2.6.15 kernel (eventually with any suggested
patches) later today...
Thanks again and best regards
J Esteves
--
+351 939838775 Skype:jmcerqueira http://del.icio.us/jmce
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2006-03-03 15:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 17:01 oom-killer: gfp_mask=0xd1 with 2.6.12 on EM64T J M Cerqueira Esteves
2006-03-02 9:17 ` Andrew Morton
2006-03-03 15:50 ` J M Cerqueira Esteves [this message]
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=440865A9.4000102@artenumerica.com \
--to=jmce@artenumerica.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ngalamba@fc.ul.pt \
--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;
as well as URLs for NNTP newsgroup(s).