Date: Sun, 18 Oct 2009 22:01:45 +0100 (BST) From: Gavin Atkinson <gavin@FreeBSD.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: dtrace profile timers still unstable? Message-ID: <20091018210042.I82400@ury.york.ac.uk> In-Reply-To: <alpine.BSF.2.00.0910161556260.7984@fledge.watson.org> References: <alpine.BSF.2.00.0910161556260.7984@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Oct 2009, Robert Watson wrote:
> In the past, I've had little luck using the DTrace profile timers on FreeBSD
> for much without crashes, and this morning was no different. I attempted to
> use the following(ish) script:
>
> profile-1ms
> {
>
> @data[stack()] = count();
> }
>
> The result was:
>
> 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...
Gavin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091018210042.I82400>