Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756094AbZDVRWr (ORCPT ); Wed, 22 Apr 2009 13:22:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751366AbZDVRWh (ORCPT ); Wed, 22 Apr 2009 13:22:37 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.124]:50326 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750704AbZDVRWh (ORCPT ); Wed, 22 Apr 2009 13:22:37 -0400 Date: Wed, 22 Apr 2009 13:22:34 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Jeremy Fitzhardinge cc: Frederic Weisbecker , Ingo Molnar , LKML , Andrew Morton , Glauber de Oliveira Costa , Chris Wright , Rusty Russell Subject: Re: [PATCH 0/2] [GIT PULL] tracing: various bug fixes In-Reply-To: <49EF5138.3030408@goop.org> Message-ID: References: <20090420222257.267399830@goodmis.org> <20090421082354.GC12512@elte.hu> <20090421094616.GA14561@elte.hu> <20090422114750.GA14202@nowhere> <20090422171047.GA5975@nowhere> <49EF5138.3030408@goop.org> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1196 Lines: 40 On Wed, 22 Apr 2009, Jeremy Fitzhardinge wrote: > > > > > > > Do you have CONFIG_PARAVIRT on? When I disabled it, I have yet to > > > reproduce the bug. But I've only rebooted a few times. I'm going to > > > continue to reboot to see if I can trigger it. > > > > > > > > > Yes it is enabled. > > > > > > > > > > > I'm thinking that the paravirt alternative code may have clobbered a > > > register in either the enable or disabling of interrupts. This might cause > > > a strange value to go into the hardirqs_enabled flag. > > > > > > > > > > > Ok I will try it without PARAVIRT and tell you if I can reproduce it. > > > > Interesting. What code is generated for native_irq_enable/disable? Note, when I take my standard config and enable PARAVIRT and LOCKDEP it still boots up fine. It may be a combination of some configs :-/ I'm currently doing a "config bisect" to find out what configs are needed. -- 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/