From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 5 03:40:01 2014 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A561ECC for ; Sun, 5 Jan 2014 03:40:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 78ADC1AF9 for ; Sun, 5 Jan 2014 03:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s053e1XA071627 for ; Sun, 5 Jan 2014 03:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s053e1ch071626; Sun, 5 Jan 2014 03:40:01 GMT (envelope-from gnats) Date: Sun, 5 Jan 2014 03:40:01 GMT Message-Id: <201401050340.s053e1ch071626@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org Cc: From: Mark Johnston Subject: Re: amd64/185290: Dtrace does not work on -stable/10 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Mark Johnston List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jan 2014 03:40:01 -0000 The following reply was made to PR amd64/185290; it has been noted by GNATS. From: Mark Johnston To: Robert David , bug-followup@FreeBSD.org Cc: Subject: Re: amd64/185290: Dtrace does not work on -stable/10 Date: Sat, 4 Jan 2014 22:34:55 -0500 On Mon, Dec 30, 2013 at 08:50:01PM +0000, Robert David wrote: > The following reply was made to PR amd64/185290; it has been noted by GNATS. > > From: Robert David > To: Mark Johnston > Cc: bug-followup@FreeBSD.org > Subject: Re: amd64/185290: Dtrace does not work on -stable/10 > Date: Mon, 30 Dec 2013 21:43:06 +0100 > > Hi, > > I got the system installed on my notebook and now does not have any > jail set up. > > Tried to move io.d out: > > root@notebook ~src (git)-[53624fa...] # > mv /usr/lib/dtrace/io.d /usr/lib/dtrace/io.d.bu > > root@notebook ~src (git)-[53624fa...] # dtrace -n 'syscall:::entry > { @num[execname] = count(); }' dtrace: invalid probe specifier > syscall:::entry { @num[execname] = count(); }: > "/usr/lib/dtrace/psinfo.d", line 90: failed to resolve type > kernel`struct thread * for identifier curthread: Module is no longer > loaded 1 > root@notebook ~src (git)-[53624fa...] # > > Serching through internet I found this: > http://lists.freebsd.org/pipermail/freebsd-dtrace/2013-October/000110.html > > Maybe something not backported from CURRENT. I'm testing 10.0-RC4 in a bhyve instance, and DTrace seems to be working properly. I will upgrade to stable/10 and test some more, but pretty much nothing has changed DTrace-wise between releng/10 and stable/10 so far. Moreover, the problems you're seeing tend to be the result of corrupted or absent CTF data, rather than bugs in the code. So here are a few more questions that'll help us pinpoint what's going on: - What happens when you run "ctfdump /boot/kernel/kernel"? Could you send the output? If it's correct, it should contain many thousands of lines. - Did you build the GENERIC kernel that you reported as having the issue? Do you have anything in make.conf or src.conf? - You mentioned that you have all of the probes (dtrace -l); do they have type info? For example, the command below gives the types for the arguments to read(2). Are they present when you run the same command? # dtrace -lv -n syscall:freebsd:read:entry ID PROVIDER MODULE FUNCTION NAME 38182 syscall freebsd read entry Probe Description Attributes Identifier Names: Private Data Semantics: Private Dependency Class: Unknown Argument Attributes Identifier Names: Private Data Semantics: Private Dependency Class: ISA Argument Types args[0]: int args[1]: void * args[2]: size_t Thanks! -Mark