daily CVS update output

2023-08-01 Thread NetBSD source update
Updating src tree: P src/bin/ed/cbc.c P src/bin/rcp/rcp.c P src/crypto/external/bsd/netpgp/dist/src/netpgpverify/sha2.c P src/crypto/external/bsd/openssh/dist/scp.c P src/dist/pf/sbin/pfctl/pfctl_radix.c P src/distrib/sets/lists/base/ad.mips P src/distrib/sets/lists/base/mi P src/distrib/sets/lis

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

2023-08-01 Thread Brad Spencer
Taylor R Campbell writes: > [1:text/plain Hide] > >> Date: Tue, 01 Aug 2023 16:02:17 -0400 >> From: Brad Spencer >> >> Taylor R Campbell writes: >> >> > So I just added a printf to the kernel in case this jump happens. Can >> > you update to xen_clock.c 1.15 (and sys/arch/x86/include/cpu.h 1

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

2023-08-01 Thread Taylor R Campbell
> Date: Tue, 01 Aug 2023 16:02:17 -0400 > From: Brad Spencer > > Taylor R Campbell writes: > > > So I just added a printf to the kernel in case this jump happens. Can > > you update to xen_clock.c 1.15 (and sys/arch/x86/include/cpu.h 1.135) > > and try again? > > Sure... Correction: xen_cloc

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

2023-08-01 Thread Brad Spencer
Taylor R Campbell writes: >> Date: Mon, 31 Jul 2023 12:47:20 -0400 >> >> # dtrace -x nolibs -n 'sdt:xen:hardclock:jump { @ = quantize(arg1 - arg0) } >> sdt:xen:hardclock:jump /arg2 >= 430/ { printf("hardclock jump violated >> timecounter contract") }' >> dtrace: description 'sdt:xen:hardclock:

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

2023-08-01 Thread Taylor R Campbell
> Date: Mon, 31 Jul 2023 12:47:20 -0400 > > # dtrace -x nolibs -n 'sdt:xen:hardclock:jump { @ = quantize(arg1 - arg0) } > sdt:xen:hardclock:jump /arg2 >= 430/ { printf("hardclock jump violated > timecounter contract") }' > dtrace: description 'sdt:xen:hardclock:jump ' matched 2 probes > dtrace:

Re: Why can't a WireGuard interface route packets to itself?

2023-08-01 Thread logothesia
> > route(8) for a while, and all my attempts to coax it into inserting a > > route to an interface in a different subnet than the gateway's so far > > have failed. > > route add -iface > > should work. Like this? (after deleting the original route) % sudo route add 10.0.0.1 lo0 -iface route:

Re: Why can't a WireGuard interface route packets to itself?

2023-08-01 Thread Martin Husemann
On Mon, Jul 31, 2023 at 11:59:12PM +0200, logothesia wrote: > route(8) for a while, and all my attempts to coax it into inserting a > route to an interface in a different subnet than the gateway's so far > have failed. route add -iface should work. > > I expect that you will need to dig deeper