From nobody Mon Jul 25 15:37:06 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ls40k54XFz4Xm8C for ; Mon, 25 Jul 2022 15:37:10 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ls40j73X1z3Mc1; Mon, 25 Jul 2022 15:37:09 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4004a.ext.cloudfilter.net ([10.228.9.227]) by cmsmtp with ESMTP id FzKMow6TrS8WrG08qokDL5; Mon, 25 Jul 2022 15:37:08 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id G08pooHtwGRNlG08qoa0r0; Mon, 25 Jul 2022 15:37:08 +0000 X-Authority-Analysis: v=2.4 cv=Sfrky9du c=1 sm=1 tr=0 ts=62deb8a4 a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=RgO8CyIxsXoA:10 a=VxmjJ2MpAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=hk3Yo9kxTOJDQFvJsrMA:9 a=CjuIK1q_8ugA:10 a=tuWILHVPEjkA:10 a=7gXAzLPJhVmCkEl4_tsf:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTP id DB6A915B; Mon, 25 Jul 2022 08:37:06 -0700 (PDT) Received: by slippy.cwsent.com (Postfix, from userid 1000) id A2BB3A6; Mon, 25 Jul 2022 08:37:06 -0700 (PDT) X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7+dev Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Mark Johnston cc: Cy Schubert , freebsd-current@freebsd.org, chuck@freebsd.org Subject: Re: DTrace Error In-reply-to: References: <20220723035223.57CDBD7@slippy.cwsent.com> <20220723141444.85620189@slippy.cwsent.com> <20220723185533.9EA7D11E@slippy.cwsent.com> <20220724030857.B57FAFC@slippy.cwsent.com> <20220724170719.139BB40F@slippy.cwsent.com> Comments: In-reply-to Mark Johnston message dated "Mon, 25 Jul 2022 11:26:57 -0400." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Jul 2022 08:37:06 -0700 Message-Id: <20220725153706.A2BB3A6@slippy.cwsent.com> X-CMAE-Envelope: MS4xfBKxQBoMWrp1CNdVHbh5j5GK5Bgepl2N2ivGbT2cPd7STymFeJafjA2wuCoO7hnVXKpjzXoRr34ZB91tx5+65+7HHmO5ZuFXVjSc4zlPCHI0TZqZ9xPU uB78RbIxiFudXAuiCrZq/Xv2EQZhjqMMtFVFeXm1gYpztdhB5hV8yvjK9L9Rh4Mv1+if9JZZAIgH0+d9OhBRwmFIWAkjX7nicjuEwBYrNIfAuS6PnCGQ4Yir YD1z5JGqE28n+USqGoYD/Wg6uKKy288C419zFWhov6I= X-Rspamd-Queue-Id: 4Ls40j73X1z3Mc1 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 3.97.99.32) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-1.80 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; MV_CASE(0.50)[]; RCVD_IN_DNSWL_MED(-0.20)[3.97.99.32:from]; MIME_GOOD(-0.10)[text/plain]; HAS_REPLYTO(0.00)[Cy.Schubert@cschubert.com]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US]; REPLYTO_EQ_FROM(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[cschubert.com: no valid DMARC record]; RCVD_TLS_LAST(0.00)[] X-ThisMailContainsUnwantedMimeParts: N In message , Mark Johnston writes: > On Sun, Jul 24, 2022 at 10:07:19AM -0700, Cy Schubert wrote: > > In message <20220724030857.B57FAFC@slippy.cwsent.com>, Cy Schubert writes: > > > In message <20220723185533.9EA7D11E@slippy.cwsent.com>, Cy Schubert write > s: > > > > In message , Mark Johnston writes: > > > > > On Sat, Jul 23, 2022 at 07:14:44AM -0700, Cy Schubert wrote: > > > > > > In message <20220723035223.57CDBD7@slippy.cwsent.com>, Cy Schubert > writ > > > es > > > > : > > > > > > > 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 d > trac > > > e > > > > > > > command entered, whether it be a fbt or sdt, the following error > occu > > > rs > > > > : > > > > > > > > > > > > > > slippy# dtrace -n 'fbt::ieee80211_vap_setup:entry { printf("enter > ing > > > > > > > ieee80211_vap_setup\n"); }' > > > > > > > dtrace: invalid probe specifier fbt::ieee80211_vap_setup:entry { > > > > > > > printf("entering ieee80211_vap_setup\n"); }: "/usr/lib/dtrace/psi > nfo. > > > d" > > > > , > > > > > > > line 1: failed to copy type of 'pr_gid': Conflicting type is alre > ady > > > de > > > > fi > > > > > ned > > > > > > > slippy# > > > > > > > > > > > > > > Old DTrace scripts I've used months or even years ago also fail w > ith > > > th > > > > e > > > > > > > same error. It's not this one probe. All probes result in the pr_ > gid > > > er > > > > ro > > > > > r. > > > > > > > > > > > > > > I'm currently rebuilding my "prod" tree from scratch with the hop > e th > > > at > > > > > > > > > > > it's simply something out of sync. But, should it not be, has any > one > > > el > > > > se > > > > > > > > > > > > encountered this lately? > > > > > > > > > > > > A full clean rebuild and installworld/kernel did not change the res > ult. > > > > > > > > > This is a new problem. > > > > > > > > > > I don't see any such problem on a system built from commit 151abc80cd > e, > > > > > using GENERIC. Are you using a custom kernel config? Which kernel > > > > > modules do you have loaded? > > > > > > > > [...] > > > > > > chuck@ emailed me privately suggesting a roll back to cb2ae6163174. The > > > problem is fixed. I'm creating a special branch that reverts only the llv > m > > > commits since then. > > > > llvm 14 is not the problem. There must be something else after cb2ae6163174 > > > that is causing the regression. > > Are you able to bisect? I spent a bit of time trying to replicate the > problem based on your kernel config, without any luck yet. How fortuitous is this email. I just rebooted my sandbox again and discovered this is related to non-INVARIANT kernels. Enabling INVARIANTS "fixes" dtrace. There must be some commit since cb2ae6163174 that affected non-INVARIANT kernels. As to which one, I'm not sure yet. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org NTP: Web: https://nwtime.org e**(i*pi)+1=0