Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933644Ab2EWPOk (ORCPT ); Wed, 23 May 2012 11:14:40 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:4670 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753572Ab2EWPOi (ORCPT ); Wed, 23 May 2012 11:14:38 -0400 X-Authority-Analysis: v=2.0 cv=ae7jbGUt c=1 sm=0 a=ZycB6UtQUfgMyuk2+PxD7w==:17 a=XQbtiDEiEegA:10 a=_2gBi4Ny9w4A:10 a=5SG0PmZfjMsA:10 a=Q9fys5e9bTEA:10 a=meVymXHHAAAA:8 a=ayC55rCoAAAA:8 a=OA39FpFkUs2GtTTHs2IA:9 a=PUjeQqilurYA:10 a=ZycB6UtQUfgMyuk2+PxD7w==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.80.29 Message-ID: <1337786077.13348.161.camel@gandalf.stny.rr.com> Subject: Re: [3.4-rc3] Thread overran stack, or stack corrupted From: Steven Rostedt To: Dave Jones Cc: Linus Torvalds , Linux Kernel Date: Wed, 23 May 2012 11:14:37 -0400 In-Reply-To: <20120523150540.GA2016@redhat.com> References: <1334720611.28106.25.camel@gandalf.stny.rr.com> <20120418035004.GA31465@redhat.com> <1334721441.28106.28.camel@gandalf.stny.rr.com> <20120418040632.GB31465@redhat.com> <1334722164.28106.31.camel@gandalf.stny.rr.com> <20120418135815.GA10798@redhat.com> <1334760965.28106.39.camel@gandalf.stny.rr.com> <20120418153002.GB17558@redhat.com> <1334767425.28106.43.camel@gandalf.stny.rr.com> <1337783828.13348.158.camel@gandalf.stny.rr.com> <20120523150540.GA2016@redhat.com> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.2.2-1 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 489 Lines: 16 On Wed, 2012-05-23 at 11:05 -0400, Dave Jones wrote: > But! Linus' current tree seems to have working tracing on that box. > Don't break it again! ;-) You could install ktest and run a reverse bisect to find out what fixed it ;-) -- Steve -- 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/