From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [patch 1/4] Ignore stolen time in the softlockup watchdog Date: Tue, 24 Apr 2007 11:32:22 -0700 Message-ID: <20070424113222.ed2e1314.akpm@linux-foundation.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> <462E4969.6070802@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <462E4969.6070802@goop.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Jeremy Fitzhardinge Cc: Bhargava , Thomas@smtp2.linux-foundation.org, Lindsley , Prarit@smtp2.linux-foundation.org, john stultz , Zachary@smtp2.linux-foundation.org, Linux Kernel , Eric Dumazet , virtualization@lists.osdl.org, Chris Lalancette , Paul Mackerras , Rick@smtp2.linux-foundation.org, Martin Schwidefsky , Ingo Molnar , Gleixner List-Id: virtualization@lists.linuxfoundation.org On Tue, 24 Apr 2007 11:16:09 -0700 Jeremy Fitzhardinge wrote: > 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. Well, it _is_ mysterious. Did you try to locate the code which failed? I got lost in macros and include files, and gave up very very easily. Stop hiding, Ingo. > 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. I have whatever I pulled from firstfloor over the weekend. It's in rc7-mm1. No, it doesn't use local_save_flags. > >> 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... > That's a doddle. On test system, boot with netconsole=4444@/eth0,@/ On workstation: sudo netcat -u -l -p | tee -a ~/.log/log-