Date: Fri, 07 Apr 2017 16:30:57 +0000 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 Message-ID: <bug-218452-8-PWFF0kYbJV@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218452 --- Comment #5 from Fabian Keil <fk@fabiankeil.de> --- 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 CPU) Origin="AuthenticAMD" Id=0x60fb2 Family=0xf Model=0x6b Stepping=2 Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x2001<SSE3,CX16> AMD Features=0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!> AMD Features2=0x11f<LAHF,CMP,SVM,ExtAPIC,CR8,Prefetch> SVM: NAsids=64 real memory = 4294967296 (4096 MB) avail memory = 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 usec to 2192 usec for pid 43082 (getty) Apr 7 18:10:04 kendra kernel: calcru: runtime went backwards from 33837 usec 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 usec to 829154 usec for pid 88073 (perl) Apr 7 18:10:04 kendra kernel: calcru: runtime went backwards from 1228 usec 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 usec 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. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218452-8-PWFF0kYbJV>