From owner-freebsd-current@FreeBSD.ORG Fri Sep 10 14:31:39 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C6431065679 for ; Fri, 10 Sep 2010 14:31:39 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 307458FC1E for ; Fri, 10 Sep 2010 14:31:39 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:6c87:9302:5653:307d] (unknown [IPv6:2001:7b8:3a7:0:6c87:9302:5653:307d]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 197525C61; Fri, 10 Sep 2010 16:31:38 +0200 (CEST) Message-ID: <4C8A414C.6000603@FreeBSD.org> Date: Fri, 10 Sep 2010 16:31:40 +0200 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.10pre) Gecko/20100910 Lanikai/3.1.4pre MIME-Version: 1.0 To: "Thomas E. Spanjaard" References: <4C8A379E.6080909@deepbone.net> In-Reply-To: <4C8A379E.6080909@deepbone.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Eventtimers b0rking w/ math/atlas X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 14:31:39 -0000 On 2010-09-10 15:50, Thomas E. Spanjaard wrote: > While trying to build math/atlas on a FreeBSD/amd64 9.0-CURRENT r212411, > the kernel hangs at some point when math/atlas tries to run some tests > (presumably the ones to profile the code and optimise). The kernel > spouts messages about Starting event timers: LAPIC @ 1000Hz, HPET @ > 127Hz; then LAPIC @ 1000Hz, HPET @ 8128Hz (iirc), back, then back again. It's probably running profiled executables (e.g. compiled with -pg)? This can lead to the above messages, and apparently also to deadlocks. I am not sure what to do about it though, except confirm that this is very likely your problem...