mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jfock@abas-projektierung.de
To: linux-kernel@vger.kernel.org
Subject: Re-2: oom-killer: gfp_mask=0xd1  with 2.6.12 on EM64T
Date: 03 Mar 2006 16:03:04 UT	[thread overview]
Message-ID: <000702D2.440876C7@192.168.222.27> (raw)


I have The same Problem with a Maxdata Server 5220l with 8GB memory 2 Intel Xeon Processors und an Intel Raidcontroler
Since im Using Linux-2.6.15.4 from Kernel.org my System is OK
Johann
Abas Projektierung GmbH



-------- Original Message --------
Subject: Re: oom-killer: gfp_mask=0xd1  with 2.6.12 on EM64T (03-Mrz-2006 16:50)
From:    jmce@artenumerica.com
To:      jfock@abas-projektierung.de

> 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
> 


To: jmce@artenumerica.com
    linux-kernel@vger.kernel.org
Cc: support@artenumerica.com
    ngalamba@fc.ul.pt


                 reply	other threads:[~2006-03-03 16:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=000702D2.440876C7@192.168.222.27 \
    --to=jfock@abas-projektierung.de \
    --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®