mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-kernel@vger.kernel.org, jk@novozymes.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Yinghai Lu <yinghai@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Tejun Heo <tj@kernel.org>
Subject: Re: Memory issues with Opteron 6220
Date: Thu, 9 Feb 2012 14:23:59 +0100	[thread overview]
Message-ID: <20120209132359.GA8830@elte.hu> (raw)
In-Reply-To: <1328778529.2374.2.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>


* Eric Dumazet <eric.dumazet@gmail.com> wrote:

> Le jeudi 09 février 2012 à 09:33 +0100, Ingo Molnar a écrit :
> > * Anders Ossowicki <aowi@novozymes.com> wrote:
> > 
> > > Hey,
> > > 
> > > We're seeing unexpected slowdowns and other memory issues with a new system.
> > > Enough to render it unusable. For example:
> > > 
> > > Error: open3: fork failed: Cannot allocate memory
> > > 
> > > at times where there's no real memory pressure:
> > >                    total       used       free     shared    buffers     cached
> > >       Mem:     132270720  131942388     328332          0     299768  103334420
> > >       -/+ buffers/cache:   28308200  103962520
> > >       Swap:      7811068      13760    7797308
> > >
> > > [...]
> > 
> > > The system is a Dell Poweredge R715, with two eight-core 
> > > Opteron 6220 processors and 128G of memory. We have several 
> > > similar systems, such as the one this should replace: R715, 
> > > 2x8 core Opteron 6140, 128G memory, and they do not exhibit 
> > > any similar symptoms.
> > 
> > 130 MB of RAM visible to Linux isn't the expected bootup default 
> > indeed. Around 130 *GB* would be expected ...
> 
> Not sure what you mean, I see 128GB in the "free" output, as 
> expected.

Erm, yes. I plead temporary blindness!

So all RAM is visible properly. This error:

> > > Error: open3: fork failed: Cannot allocate memory

suggests allocation failure. How is that possible with so much 
RAM?

Thanks,

	Ingo

  reply	other threads:[~2012-02-09 13:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 14:37 Anders Ossowicki
2012-02-09  8:33 ` Ingo Molnar
2012-02-09  9:08   ` Eric Dumazet
2012-02-09 13:23     ` Ingo Molnar [this message]
2012-02-09 21:07   ` Jesper Krogh
2012-02-10 15:21     ` Jesper Krogh
2012-02-11 13:48       ` Ingo Molnar
2012-02-14  9:32         ` Anders Ossowicki
     [not found] ` <20120208205628.GA18909@alberich.amd.com>
2012-02-09 12:43   ` Anders Ossowicki
2012-02-09 13:28     ` Ingo Molnar
2012-02-09 13:49       ` Anders Ossowicki
2012-02-09 16:11         ` Yinghai Lu
2012-02-09 17:51           ` Anders Ossowicki
2012-02-09 18:56             ` Yinghai Lu
2012-02-11 13:50               ` Ingo Molnar

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=20120209132359.GA8830@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=eric.dumazet@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jk@novozymes.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=yinghai@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

Powered by JetHome