From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753121Ab1FEGCN (ORCPT ); Sun, 5 Jun 2011 02:02:13 -0400 Received: from mo-p00-ob.rzone.de ([81.169.146.161]:33018 "EHLO mo-p00-ob.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752554Ab1FEGCM (ORCPT ); Sun, 5 Jun 2011 02:02:12 -0400 X-RZG-AUTH: :IGUXYVOIf/Z0yAghYbpIhzghmj8icP68r1arC3zTx2B9G7/X5zri/u5Y1+fsZ6BmRA== X-RZG-CLASS-ID: mo00 Message-ID: <4DEB1BD6.6070405@die-jansens.de> Date: Sun, 05 Jun 2011 08:01:58 +0200 From: Arne Jansen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: Peter Zijlstra CC: Linus Torvalds , Ingo Molnar , hpa@zytor.com, linux-kernel@vger.kernel.org, efault@gmx.de, npiggin@kernel.dk, akpm@linux-foundation.org, frank.rowand@am.sony.com, linux-tip-commits@vger.kernel.org, Thomas Gleixner Subject: Re: [tip:sched/locking] sched: Add p->pi_lock to task_rq_lock() References: <20110405152729.232781355@chello.nl> <4DE64596.5010006@die-jansens.de> <1306946120.2497.606.camel@laptop> <4DE674EB.1000200@die-jansens.de> <1306951751.2497.626.camel@laptop> <1306953870.2497.627.camel@laptop> <4DE6936F.7090700@die-jansens.de> <1307092535.2353.2973.camel@twins> <4DE8B13D.9020302@die-jansens.de> <4DE8DC28.30709@die-jansens.de> <1307225323.2497.730.camel@laptop> In-Reply-To: <1307225323.2497.730.camel@laptop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05.06.2011 00:08, Peter Zijlstra wrote: > On Sun, 2011-06-05 at 06:29 +0900, Linus Torvalds wrote: >> On Fri, Jun 3, 2011 at 10:05 PM, Arne Jansen wrote: >>> >>> No change. Also git bisect quite clearly points to >>> 0122ec5b02f766c and ab2515c4b98f7bc4, both are older than >>> b1c43f82c5aa2654 mentioned in the other thread. >> >> Ok, I haven't heard anything further on this. Ingo? Peter? > > I'm a bit stumped, and not being able to reproduce at all :/ I'm willing to take any number of round trips to get to the true nature of the bug. From the description I have a feeling that the offending patch might just shift the timing slightly, so even if the problem is gone for me, it might just be buried deeper. I can also try to reproduce it on a second machine and give you access to it, though this might take a few days. > >> We're getting to the point where we just need to revert the thing, >> since I'm not getting the feeling that there are any fixes >> forthcoming, and I'd like -rc2 to not have this kind of bisected bug. > > Agreed. > >> Ingo? Those two commits no longer revert cleanly, presumably due to >> other changes in the area (but I didn't check). Can you do a patch to >> do the reverts, and then you can try to re-do the thing later once you >> figure out what's wrong. > > Yeah, that wants a whole lot of reverting, from the offending commit up > to and including 317f394160e9beb97d19a84c39b7e5eb3d7815a8. > > -- > 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/