Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933588Ab1D1XiH (ORCPT ); Thu, 28 Apr 2011 19:38:07 -0400 Received: from ipmail04.adl6.internode.on.net ([150.101.137.141]:10573 "EHLO ipmail04.adl6.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755445Ab1D1XiF (ORCPT ); Thu, 28 Apr 2011 19:38:05 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmUDAFr5uU15LHHJgWdsb2JhbACmABUBARYmJcZdDoVoBJx5 Date: Fri, 29 Apr 2011 09:37:51 +1000 From: Dave Chinner To: Christian Kujau Cc: LKML , xfs@oss.sgi.com Subject: Re: 2.6.39-rc4+: oom-killer busy killing tasks Message-ID: <20110428233751.GR12436@dastard> References: <20110424234655.GC12436@dastard> <20110427022655.GE12436@dastard> <20110427102824.GI12436@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1436 Lines: 42 On Thu, Apr 28, 2011 at 10:30:47AM -0700, Christian Kujau wrote: > Hi David, > > sorry for the late response: > > On Wed, 27 Apr 2011 at 20:28, Dave Chinner wrote: > > hmmmm. Speaking of which - have you changed any of the XFS tunables > > in /proc/sys/fs/xfs/ on your machine (specifically > > xfssyncd_centisecs)? > > No, I did not change anything underneath /proc/sys/fs/xfs. > > > Not easy because there are tree-wide changes that need to be > > preserved (e.g. block layer plugging changes) while others around it > > would need to be reverted.... > > Yeah, I noticed. I wanted to do something like this: > > $ for c in `git log --pretty=oneline --no-merges v2.6.38..v2.6.39-rc2 fs/xfs | awk '{print $1}'`; do > git revert $c > done > > ...but this broke on the 1st or 2nd commit because of unresolved changes. > > Now I'm in the middle of another bisect attempt, trying to reproduce but > Im getting (probably totally unrelated) warnings here: Did you read the email that pointed to CONFIG_TINY_RCU as the ptotential source of the problem? Can you change to CONFIG_TREE_RCU and see if the problem goes away? Cheers, Dave. -- Dave Chinner david@fromorbit.com -- 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/