[Bug 218452] I can cause an assertion with a dtrace script and when it does happen, dtrace fails until the module dtraceall is reloaded

[bugzilla-noreply at freebsd.org]

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

--- Comment #8 from Fabian Keil <fk at 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 that a
laptop, which ran at
sys/kern/kern_resource.c-917-            * a reduced clock frequency at boot,
kicked into high gear.
sys/kern/kern_resource.c-918-            * The wisdom of spamming this message
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 speed
via ACPI.
sys/kern/kern_resource.c-922-            */
sys/kern/kern_resource.c:923:           printf("calcru: runtime went backwards
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);

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