Date: Sun, 18 Oct 2009 23:02:11 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Gavin Atkinson <gavin@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: dtrace profile timers still unstable? Message-ID: <alpine.BSF.2.00.0910182301230.78183@fledge.watson.org> In-Reply-To: <20091018210042.I82400@ury.york.ac.uk> References: <alpine.BSF.2.00.0910161556260.7984@fledge.watson.org> <20091018210042.I82400@ury.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0910182301230.78183>