Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753017AbaFBTZm (ORCPT ); Mon, 2 Jun 2014 15:25:42 -0400 Received: from mail-qa0-f52.google.com ([209.85.216.52]:52835 "EHLO mail-qa0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752748AbaFBTZj (ORCPT ); Mon, 2 Jun 2014 15:25:39 -0400 MIME-Version: 1.0 Date: Mon, 2 Jun 2014 12:25:38 -0700 Message-ID: Subject: perf intel_pmu_handle_irq warning From: Vinson Lee To: Peter Zijlstra , Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo , Thomas Gleixner , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi. We've seen this perf-related warning with 3.10 on several different machines. When this warning occurs there are multiple instances of perf stat running. ------------[ cut here ]------------ WARNING: at arch/x86/kernel/cpu/perf_event_intel.c:1191 intel_pmu_handle_irq+0xc9/0x2cb() perfevents: irq loop stuck! Modules linked in: netconsole configfs cpufreq_ondemand ipv6 dm_multipath video sbs sbshc acpi_pad acpi_ipmi acpi_i2c i2c_core parport_pc lp parport tcp_diag inet_diag ipmi_si ipmi_ andler iTCO_wdt iTCO_vendor_support dcdbas ses enclosure bnx2 hed wmi serio_raw i7core_edac edac_core lpc_ich mfd_core microcode acpi_cpufreq freq_table mperf shpchp megaraid_sas CPU: 6 PID: 0 Comm: swapper/6 Not tainted 3.10.28 #1 0000000000000000 ffff881219c06cf8 ffffffff814bdbf8 ffff881219c06d30 ffffffff8103d453 ffff881219c06d40 0000000000000064 ffff881219c0bc90 0000000000000040 ffff88052ca35800 ffff881219c06d90 ffffffff8103d4b7 Call Trace: [] dump_stack+0x19/0x1b [] warn_slowpath_common+0x65/0x7d [] warn_slowpath_fmt+0x4c/0x4e [] intel_pmu_handle_irq+0xc9/0x2cb [] perf_event_nmi_handler+0x17/0x19 [] nmi_handle.isra.1+0x73/0xab [] ? nmi_handle.isra.1+0x5/0xab [] do_nmi+0xa7/0x2c9 [] end_repeat_nmi+0x1e/0x2e [] ? x86_pmu_disable_event+0x1b/0x1d [] ? x86_pmu_disable_event+0x1b/0x1d [] ? x86_pmu_disable_event+0x1b/0x1d <> [] intel_pmu_disable_event+0xc8/0xdf [] x86_pmu_stop+0x3a/0x9f [] x86_pmu_del+0x2f/0x9c [] event_sched_out+0x8b/0xf1 [] __perf_remove_from_context+0x3f/0x89 [] remote_function+0x17/0x40 [] generic_smp_call_function_single_interrupt+0xb8/0xe8 [] smp_call_function_single_interrupt+0x18/0x29 [] call_function_single_interrupt+0x6a/0x70 [] ? sched_clock_cpu+0x42/0xc7 [] ? cpuidle_enter_state+0x52/0xa3 [] ? cpuidle_enter_state+0x4b/0xa3 [] cpuidle_idle_call+0xe5/0x13f [] arch_cpu_idle+0xe/0x1d [] cpu_startup_entry+0x128/0x17a [] start_secondary+0x246/0x248 ---[ end trace 6259476cbb715a4d ]--- CPU#6: ctrl: 0000000000000000 CPU#6: status: 0000000000000008 CPU#6: overflow: 0000000000000000 CPU#6: fixed: 00000000000000bb CPU#6: pebs: 0000000000000000 CPU#6: active: 0000000300000003 CPU#6: gen-PMC0 ctrl: 0000000000530151 CPU#6: gen-PMC0 count: 0000ffff8154731e CPU#6: gen-PMC0 left: 000000007eab8d8a CPU#6: gen-PMC1 ctrl: 00000000005301b7 CPU#6: gen-PMC1 count: 0000ffff800ac9b4 CPU#6: gen-PMC1 left: 000000007ff53654 CPU#6: gen-PMC2 ctrl: 0000000000000000 CPU#6: gen-PMC2 count: 0000000000000000 CPU#6: gen-PMC2 left: 000000006adea321 CPU#6: gen-PMC3 ctrl: 000000000013003c CPU#6: gen-PMC3 count: 0000000000000000 CPU#6: gen-PMC3 left: 0000000000008d7e CPU#6: fixed-PMC0 count: 0000ffffdf0acb67 CPU#6: fixed-PMC1 count: 0000ffffc2f1a0bd CPU#6: fixed-PMC2 count: 0000000000000000 perf_event_intel: clearing PMU state on CPU#6 Cheers, Vinson -- 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/