From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755451AbaHFOgs (ORCPT ); Wed, 6 Aug 2014 10:36:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:24079 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754225AbaHFOgf (ORCPT ); Wed, 6 Aug 2014 10:36:35 -0400 Date: Wed, 6 Aug 2014 10:36:21 -0400 From: Dave Jones To: Linux Kernel Cc: a.p.zijlstra@chello.nl Subject: perf related boot hang. Message-ID: <20140806143621.GA13832@redhat.com> Mail-Followup-To: Dave Jones , Linux Kernel , a.p.zijlstra@chello.nl MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Linus current tree, when I cold-boot one of my boxes, it locks up during boot up with this trace.. Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 2 CPU: 2 PID: 577 Comm: in:imjournal Not tainted 3.16.0+ #33 ffff880244c06c88 000000008b73013e ffff880244c06bf0 ffffffffb47ee207 ffffffffb4c51118 ffff880244c06c78 ffffffffb47ebcf8 0000000000000010 ffff880244c06c88 ffff880244c06c20 000000008b73013e 0000000000000000 Call Trace: [] dump_stack+0x4e/0x7a [] panic+0xd4/0x207 [] watchdog_overflow_callback+0x118/0x120 [] __perf_event_overflow+0xae/0x350 [] ? perf_event_task_disable+0xa0/0xa0 [] ? x86_perf_event_set_period+0xbf/0x150 [] perf_event_overflow+0x14/0x20 [] intel_pmu_handle_irq+0x206/0x410 [] perf_event_nmi_handler+0x2b/0x50 [] nmi_handle+0xd2/0x390 [] ? nmi_handle+0x5/0x390 [] ? lock_acquired+0x131/0x450 [] default_do_nmi+0x72/0x1c0 If I reset it, it then seems to always boot up fine. Dave