Date: Sat, 23 Jul 2022 14:39:42 -0400 From: Mark Johnston <markj@freebsd.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: freebsd-current@freebsd.org Subject: Re: DTrace Error Message-ID: <YtxAbplpPtLy2Ll1@nuc> In-Reply-To: <20220723141444.85620189@slippy.cwsent.com> References: <20220723035223.57CDBD7@slippy.cwsent.com> <20220723141444.85620189@slippy.cwsent.com>
index | next in thread | previous in thread | raw e-mail
On Sat, Jul 23, 2022 at 07:14:44AM -0700, Cy Schubert wrote:
> In message <20220723035223.57CDBD7@slippy.cwsent.com>, Cy Schubert writes:
> > I'm not sure if this is because my obj tree needs a fresh rebuild and
> > reinstall or if this is a legitimate problem. Regardless of the dtrace
> > command entered, whether it be a fbt or sdt, the following error occurs:
> >
> > slippy# dtrace -n 'fbt::ieee80211_vap_setup:entry { printf("entering
> > ieee80211_vap_setup\n"); }'
> > dtrace: invalid probe specifier fbt::ieee80211_vap_setup:entry {
> > printf("entering ieee80211_vap_setup\n"); }: "/usr/lib/dtrace/psinfo.d",
> > line 1: failed to copy type of 'pr_gid': Conflicting type is already defined
> > slippy#
> >
> > Old DTrace scripts I've used months or even years ago also fail with the
> > same error. It's not this one probe. All probes result in the pr_gid error.
> >
> > I'm currently rebuilding my "prod" tree from scratch with the hope that
> > it's simply something out of sync. But, should it not be, has anyone else
> > encountered this lately?
>
> A full clean rebuild and installworld/kernel did not change the result.
> This is a new problem.
I don't see any such problem on a system built from commit 151abc80cde,
using GENERIC. Are you using a custom kernel config? Which kernel
modules do you have loaded?
It might be useful to see a ctfdump -S of your kernel, to confirm that
you're using CTFv3.
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YtxAbplpPtLy2Ll1>