From owner-freebsd-bugs@freebsd.org  Sat Apr  8 10:34:21 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 AF7C7D33001
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat,  8 Apr 2017 10:34:21 +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 96561F2A
 for <freebsd-bugs@FreeBSD.org>; Sat,  8 Apr 2017 10:34:21 +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 v38AYLov052255
 for <freebsd-bugs@FreeBSD.org>; Sat, 8 Apr 2017 10:34:21 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: Sat, 08 Apr 2017 10:34:21 +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 Some People
X-Bugzilla-Who: fk@fabiankeil.de
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-aATFIQNXr9@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: Sat, 08 Apr 2017 10:34:21 -0000

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

--- Comment #8 from Fabian Keil <fk@fabiankeil.de> ---
The calcru complaints I'm getting don't depend on debug flags:

sys/kern/kern_resource.c-914-   } else { /* tu < ruxp->rux_tu */
sys/kern/kern_resource.c-915-           /*
sys/kern/kern_resource.c-916-            * What happened here was likely th=
at a
laptop, which ran at
sys/kern/kern_resource.c-917-            * a reduced clock frequency at boo=
t,
kicked into high gear.
sys/kern/kern_resource.c-918-            * The wisdom of spamming this mess=
age
in that case is
sys/kern/kern_resource.c-919-            * dubious, but it might also be
indicative of something
sys/kern/kern_resource.c-920-            * serious, so lets keep it and hope
laptops can be made
sys/kern/kern_resource.c-921-            * more truthful about their CPU sp=
eed
via ACPI.
sys/kern/kern_resource.c-922-            */
sys/kern/kern_resource.c:923:           printf("calcru: runtime went backwa=
rds
from %ju usec "
sys/kern/kern_resource.c-924-               "to %ju usec for pid %d (%s)\n",
sys/kern/kern_resource.c-925-               (uintmax_t)ruxp->rux_tu,
(uintmax_t)tu,
sys/kern/kern_resource.c-926-               p->p_pid, p->p_comm);

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