Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965162AbWH2RMW (ORCPT ); Tue, 29 Aug 2006 13:12:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965166AbWH2RMW (ORCPT ); Tue, 29 Aug 2006 13:12:22 -0400 Received: from adsl-69-232-92-238.dsl.sndg02.pacbell.net ([69.232.92.238]:21419 "EHLO gnuppy.monkey.org") by vger.kernel.org with ESMTP id S965162AbWH2RMV (ORCPT ); Tue, 29 Aug 2006 13:12:21 -0400 Date: Tue, 29 Aug 2006 10:11:54 -0700 To: Robert Crocombe Cc: Esben Nielsen , Ingo Molnar , Thomas Gleixner , rostedt@goodmis.org, linux-kernel , "Bill Huey (hui)" Subject: Re: rtmutex assert failure (was [Patch] restore the RCU callback...) Message-ID: <20060829171154.GA11627@gnuppy.monkey.org> References: <20060823210558.GA17606@gnuppy.monkey.org> <20060823210842.GB17606@gnuppy.monkey.org> <20060824014658.GB19314@gnuppy.monkey.org> <20060825071957.GA30720@gnuppy.monkey.org> <20060826104923.GA7879@gnuppy.monkey.org> <20060828202827.GA3625@gnuppy.monkey.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11+cvs20060403 From: Bill Huey (hui) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1784 Lines: 40 On Mon, Aug 28, 2006 at 09:05:27PM -0700, Robert Crocombe wrote: > On 8/28/06, hui Bill Huey wrote: > > >I was unclear in explain that __put_task_struct() should never > >appear with free_task() in a stack trace as you can clearly see > >from the implementation. All it's suppose to do is wake a thread, > >so "how?" you're getting those things simultaneously in the stack > >trace is completely baffling to me. Could you double check to see > >if it's booting the right kernel ? maybe make sure that's calling > >that version of the function with printks or something ? > > So I built another kernel with the most recent "t6" patches from > scratch and stuck in a directory 2.6.17-rt8-mrproper. > > [rcrocomb@spanky ~]$ cd kernel/ > [rcrocomb@spanky kernel]$ rm -Rf test_2.6.17-rt8/ > [rcrocomb@spanky kernel]$ tar xf source/linux-2.6.16.tar > [rcrocomb@spanky kernel]$ mv linux-2.6.16/ 2.6.17-rt8-mrproper > [rcrocomb@spanky kernel]$ cd 2.6.17-rt8-mrproper/ > [rcrocomb@spanky 2.6.17-rt8-mrproper]$ patch -s -p1 < > ../patches/patch-2.6.17 > [rcrocomb@spanky 2.6.17-rt8-mrproper]$ patch -s -p1 < > ../patches/patch-2.6.17-rt8 > [rcrocomb@spanky 2.6.17-rt8-mrproper]$ patch -s -p0 < ../patches/t6.diff > [rcrocomb@spanky 2.6.17-rt8-mrproper]$ uname -r > 2.6.17-rt8_UP_00 I'm going to ask what seems like a really stupid question. What's "t6" ? and what's the relationship of that to my patches ? [side note: I'm headed to Burning Man tomorrow and won't be on a computer for 6 days until I come back] bill - 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/