linux-kernel - Re: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels

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: <alpine.DEB.2.00.1006011351400.13136@chino.kir.corp.google.com>
Date:	Tue, 1 Jun 2010 13:52:13 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	dave b <db.pub.mail@...il.com>
cc:	Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Subject: Re: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels

On Thu, 27 May 2010, dave b wrote:

> That was just a simple test case with dd. That test case might be
> invalid - but it is trying to trigger out of memory - doing this any
> other way still causes the problem. I note that playing with some bios
> settings I was actually able to trigger what appeared to be graphics
> corruption issues when I launched kde applications ... nothing shows
> up in dmesg so this might just be a conflict between xorg and the
> kernel with those bios settings...
> 
> Anyway, This is no longer a 'problem' for me since I disabled
> overcommit and altered the values for dirty_ratio and
> dirty_background_ratio - and I cannot trigger it.
> 

Disabling overcommit should always do it, but I'd be interested to know if 
restoring dirty_ratio to 40 would help your usecase.
--
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/