Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754082AbZDVRLM (ORCPT ); Wed, 22 Apr 2009 13:11:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752892AbZDVRK5 (ORCPT ); Wed, 22 Apr 2009 13:10:57 -0400 Received: from ey-out-2122.google.com ([74.125.78.26]:8615 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752740AbZDVRK4 (ORCPT ); Wed, 22 Apr 2009 13:10:56 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=S5lAGPwBEKxs8yDS1JeOk25Rg0/ggemeYF7vj3k87Rd9FgEA9BxAiYtJNgzQWdUAoo 9wn1a9QGz+c9DZ5BGPGOOghajoT2lPOvCFfwyMfB3Qn6l3Lb1QEjANmdmHqgX+uUj1ZL lpy8CjaxqS+JQ03WYJ7F5fkv9Hrnwa0yJQTrc= Date: Wed, 22 Apr 2009 19:10:51 +0200 From: Frederic Weisbecker To: Steven Rostedt Cc: Ingo Molnar , LKML , Andrew Morton , Glauber de Oliveira Costa , Chris Wright , Jeremy Fitzhardinge , Rusty Russell Subject: Re: [PATCH 0/2] [GIT PULL] tracing: various bug fixes Message-ID: <20090422171047.GA5975@nowhere> References: <20090420222257.267399830@goodmis.org> <20090421082354.GC12512@elte.hu> <20090421094616.GA14561@elte.hu> <20090422114750.GA14202@nowhere> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2497 Lines: 75 On Wed, Apr 22, 2009 at 09:49:14AM -0400, Steven Rostedt wrote: > > > > On Wed, 22 Apr 2009, Frederic Weisbecker wrote: > > > > > > I spent the entire day (and half the night) debugging this. I was fighting > > > a case where the hardirqs_enabled flag in the task struct (lockdep flag) > > > was mysteriously being set and cleared. I stepped through the entire > > > kernel thread fork process (that was an exercise) and could not find > > > anything wrong. > > > > > > Sometimes it would go away with printk's sometimes it would not. This was > > > driving me crazy, until I noticed that paravirt was enabled. > > > > > > Turning off paravirtualization here (so far) makes everything run > > > smoothly. > > > > > > Thus my theory is that there's something fishy with the modifying of the > > > irq enable/disable code when the system detects that it is running on bare > > > hardware. > > > > > > I'm too tired to look at this more. Ingo supplied a config to play with. > > > You can disable VSMP too and it will still trigger the crash. > > > > > > -- Steve > > > > > > > It's indeed a tricky one. I can reproduce it too, I will > > try to manage having an irqsoff trace at this point, hopefully I > > could get the source of this irq disabling... > > It doesn't disable interrupts :-/ > > It is the hardirqs_enabled flag in the task struct that mysteriously turns > off and back on. I put in printks when it is off in fork, and the next > printk shows that it turns back on (between the printks!!!). > > I printed the output of "irqs_disabled()" on each of these printks and > interrupts are always enabled. It is only the hardirqs_enabled flag that > is giving strange outputs. Oh, weird... > 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. > Thanks, > > -- 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/