From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail172.messagelabs.com (mail172.messagelabs.com [216.82.254.3]) by kanga.kvack.org (Postfix) with SMTP id D13926B002D for ; Fri, 21 Oct 2011 18:07:44 -0400 (EDT) From: =?utf-8?q?Pawe=C5=82_Sikora?= Subject: Re: kernel 3.0: BUG: soft lockup: find_get_pages+0x51/0x110 Date: Fri, 21 Oct 2011 23:36:46 +0200 References: <201110122012.33767.pluto@agmk.net> <2109011.boM0eZ0ZTE@pawels> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-Id: <201110212336.47267.pluto@agmk.net> Sender: owner-linux-mm@kvack.org List-ID: To: Nai Xia Cc: Hugh Dickins , arekm@pld-linux.org, Linus Torvalds , linux-mm@kvack.org, Mel Gorman , jpiszcz@lucidpixels.com, linux-kernel@vger.kernel.org, Andrew Morton , Andrea Arcangeli On Friday 21 of October 2011 11:07:56 Nai Xia wrote: > On Fri, Oct 21, 2011 at 4:07 PM, Pawel Sikora wrote: > > On Friday 21 of October 2011 14:22:37 Nai Xia wrote: > > > >> And as a side note. Since I notice that Pawel's workload may include OOM, > > > > my last tests on patched (3.0.4 + migrate.c fix + vserver) kernel produce full cpu load > > on dual 8-cores opterons like on this htop screenshot -> http://pluto.agmk.net/kernel/screen1.png > > afaics all userspace applications usualy don't use more than half of physical memory > > and so called "cache" on htop bar doesn't reach the 100%. > > OKi 1/4 ?did you logged any OOM killing if there was some memory usage burst? > But, well my above OOM reasoning is a direct short cut to imagined > root cause of "adjacent VMAs which > should have been merged but in fact not merged" case. > Maybe there are other cases that can lead to this or maybe it's > totally another bug.... i don't see any OOM killing with my conservative settings (vm.overcommit_memory=2, vm.overcommit_ratio=100). > But still I think if my reasoning is good, similar bad things will > happen again some time in the future, > even if it was not your case here... > > > > > the patched kernel with disabled CONFIG_TRANSPARENT_HUGEPAGE (new thing in 2.6.38) > > died at night, so now i'm going to disable also CONFIG_COMPACTION/MIGRATION in next > > steps and stress this machine again... > > OK, it's smart to narrow down the range first.... disabling hugepage/compacting didn't help but disabling hugepage/compacting/migration keeps opterons stable for ~9h so far. userspace uses ~40GB (from 64) ram, caches reach 100% on htop bar, average load ~16. i wonder if it survive weekend... -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org