From owner-freebsd-current@FreeBSD.ORG  Sun Oct 18 22:02:12 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8A4F1106566C;
	Sun, 18 Oct 2009 22:02:12 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 65DEB8FC13;
	Sun, 18 Oct 2009 22:02:12 +0000 (UTC)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41])
	by cyrus.watson.org (Postfix) with ESMTPS id F343846B06;
	Sun, 18 Oct 2009 18:02:11 -0400 (EDT)
Date: Sun, 18 Oct 2009 23:02:11 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Gavin Atkinson <gavin@FreeBSD.org>
In-Reply-To: <20091018210042.I82400@ury.york.ac.uk>
Message-ID: <alpine.BSF.2.00.0910182301230.78183@fledge.watson.org>
References: <alpine.BSF.2.00.0910161556260.7984@fledge.watson.org>
	<20091018210042.I82400@ury.york.ac.uk>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: current@FreeBSD.org
Subject: Re: dtrace profile timers still unstable?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Oct 2009 22:02:12 -0000


On Sun, 18 Oct 2009, Gavin Atkinson wrote:

>> spin lock 0x849747d8 (cyclic cpu) held by 0x85442b40 (tid 100539) too long 
>> panic: spin lock held too long
>
> [...]
>
>> (I've seen panics with it pretty deterministically on i386 and amd64)
>
> Is there any particular technique to get this to panic?  I've been trying to 
> get a panic from the above script (using "dtrace -s prof.d") for a few hours 
> now without success...

The panic I saw was definitely SMP-related, and occured when I hit ctrl-c to 
terminate the script and see the results.  They were partially reported, 
followed by boom.

Robert N M Watson
Computer Laboratory
University of Cambridge