Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933872Ab3GEPPL (ORCPT ); Fri, 5 Jul 2013 11:15:11 -0400 Received: from www.linutronix.de ([62.245.132.108]:45675 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757377Ab3GEPPJ (ORCPT ); Fri, 5 Jul 2013 11:15:09 -0400 Date: Fri, 5 Jul 2013 17:15:07 +0200 (CEST) From: Thomas Gleixner To: Dave Jones cc: Linus Torvalds , Linux Kernel , Ingo Molnar , Peter Anvin , Peter Zijlstra Subject: Re: Yet more softlockups. In-Reply-To: <20130705143821.GB325@redhat.com> Message-ID: References: <20130704015525.GA8486@redhat.com> <20130705143821.GB325@redhat.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 693 Lines: 19 On Fri, 5 Jul 2013, Dave Jones wrote: > BUG: soft lockup - CPU#3 stuck for 23s! [trinity-child1:14565] > perf samples too long (2519 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 > INFO: NMI handler (perf_event_nmi_handler) took too long to run: 238147.002 msecs So we see a softlockup of 23 seconds and the perf_event_nmi_handler claims it did run 23.8 seconds. Are there more instances of NMI handler messages ? Thanks, tglx -- 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/