From owner-freebsd-bugs@freebsd.org  Fri Apr  7 17:34:48 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB754D33EBD
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri,  7 Apr 2017 17:34:48 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9A398936
 for <freebsd-bugs@FreeBSD.org>; Fri,  7 Apr 2017 17:34:48 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v37HYlAt068389
 for <freebsd-bugs@FreeBSD.org>; Fri, 7 Apr 2017 17:34:48 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 218452] I can cause an assertion with a dtrace script and when
 it does happen, dtrace fails until the module dtraceall is reloaded
Date: Fri, 07 Apr 2017 17:34:48 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kungfujesus06@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-218452-8-R9R5X8pLIm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-218452-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-218452-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 17:34:48 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218452

--- Comment #6 from Adam Stylinski <kungfujesus06@gmail.com> ---
(In reply to Fabian Keil from comment #5)

Interesting, I don't see those in /var/log/messages but maybe you're buildi=
ng
with more warning/debug stuff turned on (perhaps the invariant options?).  =
I'm
encountering this issue with just STABLE and the generic kernel and no
additional build flags.  It's possible it's machine and or virtual machine
specific, it's also possible that machines on release aren't seeing this
because assertions are turned off.  Then again, I thought that was the case=
 for
everything but CURRENT, but evidently I'm wrong on that part.

--=20
You are receiving this mail because:
You are the assignee for the bug.=