Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750786AbWIUHfl (ORCPT ); Thu, 21 Sep 2006 03:35:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750799AbWIUHfk (ORCPT ); Thu, 21 Sep 2006 03:35:40 -0400 Received: from adsl-69-232-92-238.dsl.sndg02.pacbell.net ([69.232.92.238]:8904 "EHLO gnuppy.monkey.org") by vger.kernel.org with ESMTP id S1750786AbWIUHfk (ORCPT ); Thu, 21 Sep 2006 03:35:40 -0400 Date: Thu, 21 Sep 2006 00:35:22 -0700 To: Ingo Molnar Cc: linux-kernel@vger.kernel.org, Thomas Gleixner , John Stultz , "Paul E. McKenney" , Dipankar Sarma , Arjan van de Ven , Esben Nielsen , "Bill Huey (hui)" Subject: Re: [PATCH] move put_task_struct() reaping into a thread [Re: 2.6.18-rt1] Message-ID: <20060921073522.GD10337@gnuppy.monkey.org> References: <20060920141907.GA30765@elte.hu> <20060921065624.GA9841@gnuppy.monkey.org> <20060921065402.GA22089@elte.hu> <20060921071838.GA10337@gnuppy.monkey.org> <20060921072743.GB10337@gnuppy.monkey.org> <20060921072216.GB25835@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060921072216.GB25835@elte.hu> User-Agent: Mutt/1.5.13 (2006-08-11) From: Bill Huey (hui) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1483 Lines: 31 On Thu, Sep 21, 2006 at 09:22:16AM +0200, Ingo Molnar wrote: > * Bill Huey wrote: > > > Also, triggering a panic() at the beginning of the rt mutex acquire > > was very useful since it made "in_atomic()" violations an explicit > > error stopping the machine. Stack traces started to get really crazy > > in this preemptive kernel with all sorts of things running unlike the > > non-preemptive kernel and it was time consuming to figure out the real > > stuff from the noise in the stack trace. > > well you should absolutely have serial console if you effectively want > to hack the Linux kernel. And in the serial console log you should > search for stacktraces top-down, and concentrate on the first one - any > subsequent one might be collateral damage of the first one. Of course I did that. I'm not that stupid. :) The stack traces, even with your above suggestions were too many and I had to break it down a bug at a time, stack trace at a time, since I realize problems earlier could clash and trigger other unrelated problems. It was even problematic with the serial console on which is why I did that. Maybe it was an artifact of having both the serial console and video consoles on ? 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/