Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753515Ab0LVRRM (ORCPT ); Wed, 22 Dec 2010 12:17:12 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:53419 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753414Ab0LVRRK (ORCPT ); Wed, 22 Dec 2010 12:17:10 -0500 Date: Wed, 22 Dec 2010 18:16:55 +0100 From: Ingo Molnar To: Peter Zijlstra Cc: Miklos Vajna , Mike Galbraith , shenghui , kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org, Greg KH Subject: Re: [PATCH] avoid race condition in pick_next_task_fair in kernel/sched_fair.c Message-ID: <20101222171655.GB25611@elte.hu> References: <20101219020313.GJ31750@genesis.frugalware.org> <20101222002248.GP10557@genesis.frugalware.org> <1293006589.2170.41.camel@laptop> <1293007311.11370.172.camel@marge.simson.net> <1293008842.2170.70.camel@laptop> <20101222133154.GS10557@genesis.frugalware.org> <1293026422.2170.136.camel@laptop> <1293027112.2170.140.camel@laptop> <20101222151434.GW10557@genesis.frugalware.org> <1293037718.2170.155.camel@laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1293037718.2170.155.camel@laptop> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1106 Lines: 27 * Peter Zijlstra wrote: > On Wed, 2010-12-22 at 16:14 +0100, Miklos Vajna wrote: > > kernel-build is a git build using the config I already sent and after a > > 'git checkout v2.6.36'. I can try to build master as well, so far what I > > saw is that the bug occurs there as well, but less frequently, so maybe > > that's a bit harder to debug. > > Right, so I've got v2.6.36 exploding, current -git and -tip won't > explode for me, tried both about 20 times. So I'll try and figure out > wth makes .36 explode and then see if further kernel still suffer that > problem. Does it explode if you change some of the CONFIG_CC flags, such as CONFIG_CC_OPTIMIZE_FOR_SIZE? I.e. is the crash dependent on the precise kernel image layout perhaps? If it's sensitive to that then this might keep you from chasing shadows ... Thanks, Ingo -- 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/