Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964934Ab3GEQBa (ORCPT ); Fri, 5 Jul 2013 12:01:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:10198 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751803Ab3GEQB3 (ORCPT ); Fri, 5 Jul 2013 12:01:29 -0400 Date: Fri, 5 Jul 2013 12:00:43 -0400 From: Dave Jones To: Thomas Gleixner Cc: Linus Torvalds , Linux Kernel , Ingo Molnar , Peter Anvin , Peter Zijlstra Subject: Re: Yet more softlockups. Message-ID: <20130705160043.GF325@redhat.com> Mail-Followup-To: Dave Jones , Thomas Gleixner , Linus Torvalds , Linux Kernel , Ingo Molnar , Peter Anvin , Peter Zijlstra References: <20130704015525.GA8486@redhat.com> <20130705143821.GB325@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 982 Lines: 22 On Fri, Jul 05, 2013 at 05:15:07PM +0200, Thomas Gleixner wrote: > 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 ? [ 2552.006181] perf samples too long (2511 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 [ 2552.008680] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 500392.002 msecs Dave -- 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/