daily CVS update output

2023-07-27 Thread NetBSD source update
Updating src tree: P src/doc/CHANGES P src/external/gpl3/binutils.old/dist/ld/configure.tgt P src/external/mit/xorg/lib/freetype/Makefile P src/external/mpl/dhcp/dist/common/dispatch.c P src/sys/arch/aarch64/conf/Makefile.aarch64 P src/sys/arch/arm/conf/Makefile.arm P src/sys/arch/x86/pci/amdsmn.

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

2023-07-27 Thread Brad Spencer
Taylor R Campbell writes: [snip] > I don't know what the sparc timecounter frequency is, but the Xen > system timecounter returns units of nanoseconds, i.e., runs at 1 GHz, > well within these bounds. So this kind of wraparound leading to > apparently negative runtime -- that is, l->l_stime goi

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

2023-07-27 Thread Taylor R Campbell
> Date: Thu, 27 Jul 2023 15:05:23 +1000 > from: matthew green > > one problem i've seen in kern_tc.c when the timecounter returns > a smaller value is that tc_delta() ends up returning a very large > (underflowed) value, and that makes the consumers of it do a very > wrong thing. eg, -2 becomes

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

2023-07-27 Thread Brad Spencer
Taylor R Campbell writes: > Can you please try running with the attached patch and share the > warnings it produces? Should give slightly more information. I applied the patch and caught this: [ 76783.161208] WARNING: lwp 16 (system idle/1) flags 0xa020: timecounter went backwards from (7