From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [patch 1/4] Ignore stolen time in the softlockup watchdog Date: Tue, 24 Apr 2007 11:16:09 -0700 Message-ID: <462E4969.6070802@goop.org> References: <20070327214919.800272641@goop.org> <20070327215827.871954359@goop.org> <20070423234910.50149faf.akpm@linux-foundation.org> <462E43A7.1050001@goop.org> <20070424105738.e0ce36a9.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070424105738.e0ce36a9.akpm@linux-foundation.org> Sender: linux-kernel-owner@vger.kernel.org To: Andrew Morton Cc: Ingo Molnar , Linux Kernel , virtualization@lists.osdl.org, Prarit Bhargava , Eric Dumazet , Thomas Gleixner , john stultz , Zachary Amsden , James Morris , Dan Hecht , Paul Mackerras , Martin Schwidefsky , Chris Lalancette , Rick Lindsley , Andi Kleen List-Id: virtualization@lists.linuxfoundation.org Andrew Morton wrote: > I said that because the damn thing went away when I was hunting it down > because I lost the config and was unable to remember the right combination > of debug settings. Fortunately it later came back so I took care to > preserve the config. > sched_clock doesn't *do* anything except flap interrupts. Oh, wait, have you got Andi's bugfixed version of the sched_clock patch? The first version did a local_save_flags rather than a local_irq_save. >> Hm, is it caused by using sched_clock() to generate the printk >> timestamps while generating the lock test output? >> > > Conceivably. What does that locking API test do? > Didn't make a difference here. Building your config now. > I was using printk timestamps and netconsole at the time. > Ah, great, now you're going to make me setup netconsole... J