Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756591AbZJ2TPD (ORCPT ); Thu, 29 Oct 2009 15:15:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755877AbZJ2TPC (ORCPT ); Thu, 29 Oct 2009 15:15:02 -0400 Received: from nfitmail.nfit.au.dk ([130.225.31.129]:38502 "EHLO smtp.nfit.au.dk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755037AbZJ2TPA (ORCPT ); Thu, 29 Oct 2009 15:15:00 -0400 To: linux-kernel@vger.kernel.org, mingo@elte.hu Cc: a.p.zijlstra@chello.nl, fweisbec@gmail.com, tglx@linutronix.de, acme@redhat.com, rosted@goodmis.org, paulus@samba.org Subject: Hard lockup with timer events From: Soeren Sandmann Date: 29 Oct 2009 20:15:03 +0100 Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-NFIT-RelayAddr: 130.225.16.142 X-NFIT-Solido-Score: 1. Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 902 Lines: 23 Hi, This program http://www.daimi.au.dk/~sandmann/lockup.c locks up hard for me on a Pentium 4 in 32 bit mode, with the hrtimer patches applied (-tip for example). What the program does is spawn a thread that just spins, and then 400 threads that each create a performance counter of type PERF_COUNT_SW_CPU_CLOCK and a sample period of 1000000 and a sample_type of PERF_SAMPLE_IP | PERF_SAMPLE_TID | PERF_SAMPLE_CALLCHAIN These threads then map the event buffer and read it continuously. It does not apparently lock up if SAMPLE_CALLCHAIN is removed; also I cannot get it to lock up on Core 2 Duo in either 32 or 64 bit mode. Soren -- 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/