Date: Tue, 16 Apr 2013 16:54:29 -0400 From: Mark Johnston <markjdb@gmail.com> To: Navdeep Parhar <np@FreeBSD.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, pfg@freebsd.org Subject: Re: DTrace gone quiet? Message-ID: <20130416205403.GA1409@gloom.sandvine.com> In-Reply-To: <516DAD14.9020307@FreeBSD.org> References: <516DAD14.9020307@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 16, 2013 at 12:57:08PM -0700, Navdeep Parhar wrote: > I just upgraded my kernel and userspace to head (r249552) and I notice > that DTrace doesn't output anything until I hit ctrl-c. All previous > "hits" on the probe appear lost. For example: > > # dtrace -n 'fbt::ether_output:entry' > dtrace: description 'fbt::ether_output:entry' matched 1 probe > > (No output here. I waited a long time before the ctrl-c and I know the > system is actively transmitting and receiving Ethernet traffic). > > ^C > CPU ID FUNCTION:NAME > 9 29354 ether_output:entry > 8 29354 ether_output:entry > 8 29354 ether_output:entry > 8 29354 ether_output:entry > > > Can anyone confirm or contradict this on a recent HEAD (around r249552 > in my case)? Reverting r249367 and rebuilding libdtrace+the kernel fixes the problem for me. -Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130416205403.GA1409>