linux-kernel - Re: Memory issues with Opteron 6220

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120209132359.GA8830@elte.hu>
Date:	Thu, 9 Feb 2012 14:23:59 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	linux-kernel@...r.kernel.org, jk@...ozymes.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Tejun Heo <tj@...nel.org>
Subject: Re: Memory issues with Opteron 6220


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

> Le jeudi 09 février 2012 à 09:33 +0100, Ingo Molnar a écrit :
> > * Anders Ossowicki <aowi@...ozymes.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/