Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750768AbWIUHas (ORCPT ); Thu, 21 Sep 2006 03:30:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750770AbWIUHar (ORCPT ); Thu, 21 Sep 2006 03:30:47 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:62349 "EHLO mx2.mail.elte.hu") by vger.kernel.org with ESMTP id S1750768AbWIUHar (ORCPT ); Thu, 21 Sep 2006 03:30:47 -0400 Date: Thu, 21 Sep 2006 09:22:16 +0200 From: Ingo Molnar To: Bill Huey Cc: linux-kernel@vger.kernel.org, Thomas Gleixner , John Stultz , "Paul E. McKenney" , Dipankar Sarma , Arjan van de Ven , Esben Nielsen Subject: Re: [PATCH] move put_task_struct() reaping into a thread [Re: 2.6.18-rt1] Message-ID: <20060921072216.GB25835@elte.hu> References: <20060920141907.GA30765@elte.hu> <20060921065624.GA9841@gnuppy.monkey.org> <20060921065402.GA22089@elte.hu> <20060921071838.GA10337@gnuppy.monkey.org> <20060921072743.GB10337@gnuppy.monkey.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060921072743.GB10337@gnuppy.monkey.org> User-Agent: Mutt/1.4.2.1i X-ELTE-SpamScore: -2.9 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.9 required=5.9 tests=ALL_TRUSTED,AWL,BAYES_50 autolearn=no SpamAssassin version=3.0.3 -3.3 ALL_TRUSTED Did not pass through any untrusted hosts 0.5 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.5000] -0.1 AWL AWL: From: address is in the auto white-list X-ELTE-VirusStatus: clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 975 Lines: 21 * 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. 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/