Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"

To: Brad Spencer <brad%anduin.eldar.org@localhost>
Subject: Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"
From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
Date: Fri, 28 Jul 2023 13:29:35 +0000

> Date: Fri, 28 Jul 2023 07:42:04 -0400
> From: Brad Spencer <brad%anduin.eldar.org@localhost>
> 
> dtrace: invalid probe specifier sdt:xen:hardclock:jump { @ = quantize(arg1 - arg0) } tick-10s { printa(@) }: probe description :::tick-10s does not match any probes

modload dtrace_profile

Follow-Ups:
- Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"
  - From: Brad Spencer
- Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"
  - From: Brad Spencer

References:
- Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"
  - From: Brad Spencer

Prev by Date: Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"
Next by Date: Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"
Previous by Thread: Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"
Next by Thread: Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"
Indexes:

Home | Main Index | Thread Index | Old Index