Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754305Ab0GZOGR (ORCPT ); Mon, 26 Jul 2010 10:06:17 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:57871 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753154Ab0GZOGP (ORCPT ); Mon, 26 Jul 2010 10:06:15 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=moUNKxgY+vh/sIO3mvRQFDqFcHcvGaCaZzz9m8gUYf5KwWNgZZBwOseTWDZCPRu0aZ h0JRzlFmXz9PaNWH/TbDWzOn/UX4XsCEiDtqa+16Fs2fEVm9T6IdTGrdRj2jhBBP2NqC HJld0FChMMK8nIS5ajyYEW1NvD0bfKtnXkGSM= MIME-Version: 1.0 In-Reply-To: References: From: dave b Date: Tue, 27 Jul 2010 00:05:55 +1000 Message-ID: Subject: Re: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels To: David Rientjes Cc: Hugh Dickins , linux-kernel@vger.kernel.org, linux-mm@kvack.org, KOSAKI Motohiro Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1746 Lines: 51 On 2 June 2010 06:52, David Rientjes wrote: > 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. > Actually it turns out on 2.6.34.1 I can trigger this issue. What it really is, is that linux doesn't invoke the oom killer when it should and kill something off. This is *really* annoying. I used the follow script - (on 2.6.34.1) cat ./scripts/disable_over_commit #!/bin/bash echo 2 > /proc/sys/vm/overcommit_memory echo 40 > /proc/sys/vm/dirty_ratio echo 5 > /proc/sys/vm/dirty_background_ratio And I was still able to reproduce this bug. Here is some c code to trigger the condition I am talking about. #include #include int main(void) { while(1) { malloc(1000); } return 0; } -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/