From owner-freebsd-bugs@freebsd.org Fri Apr 7 16:30:57 2017 Return-Path: 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 04D84D32EC5 for ; Fri, 7 Apr 2017 16:30:57 +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 CE47EB35 for ; Fri, 7 Apr 2017 16:30:56 +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 v37GUuqx003954 for ; Fri, 7 Apr 2017 16:30:56 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 16:30:57 +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: 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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2017 16:30:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218452 --- Comment #5 from Fabian Keil --- I'm seeing the issue on a pysical system as well. dmesg.boot excerpt: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ (2542.18-MHz K8-class C= PU) Origin=3D"AuthenticAMD" Id=3D0x60fb2 Family=3D0xf Model=3D0x6b Steppi= ng=3D2 =20 Features=3D0x178bfbff Features2=3D0x2001 AMD Features=3D0xea500800 AMD Features2=3D0x11f SVM: NAsids=3D64 real memory =3D 4294967296 (4096 MB) avail memory =3D 3984990208 (3800 MB) Event timer "LAPIC" quality 100 /var/log/messages frequently contains messages like: Apr 7 18:10:04 kendra kernel: calcru: runtime went backwards from 2321 use= c to 2192 usec for pid 43082 (getty) Apr 7 18:10:04 kendra kernel: calcru: runtime went backwards from 33837 us= ec to 32484 usec for pid 46789 (sshd) Apr 7 18:10:04 kendra kernel: calcru: runtime went backwards from 236 usec= to 233 usec for pid 45792 (g_eli[0] gpt/swap-a) Apr 7 18:10:04 kendra kernel: calcru: runtime went backwards from 878257 u= sec to 829154 usec for pid 88073 (perl) Apr 7 18:10:04 kendra kernel: calcru: runtime went backwards from 1228 use= c to 1159 usec for pid 70123 (nginx) Apr 7 18:10:04 kendra kernel: calcru: runtime went backwards from 930 usec= to 878 usec for pid 68524 (nginx) Apr 7 18:10:04 kendra kernel: calcru: runtime went backwards from 1297 use= c to 1225 usec for pid 16461 (casperd) which I believe is another symptom of the same problem. My other systems use different hardware and don't trigger the DTrace sanity check. I don't know if VirtualBox exacerbates the problem or if it simply inherits it from the system it's running on. I don't use VirtualBox and I'm not seeing the issue when using bhyve, but then again, I can only run bhyve on systems where the host system doesn't trigger the sanity checks either. --=20 You are receiving this mail because: You are the assignee for the bug.=