Re: port-xen/57535 (dtrace on Xen DOMU might need -x nolibs)

[Brad Spencer <brad%anduin.eldar.org@localhost>]

Brad Spencer <brad%anduin.eldar.org@localhost> writes:

> riastradh%NetBSD.org@localhost writes:
>
>> Synopsis: dtrace on Xen DOMU might need -x nolibs
>>
>> State-Changed-From-To: open->feedback
>> State-Changed-By: riastradh%NetBSD.org@localhost
>> State-Changed-When: Fri, 21 Jul 2023 20:13:06 +0000
>> State-Changed-Why:
>> Can you please try a clean XEN3_DOMU kernel build and report back?
>>
>> Note: You must clean the entire XEN3_DOMU kernel build directory
>> first (and cvs up or equivalent); it is not enough to do an
>> incremental build in this case.


The system disappeared from "ruptime", but wasn't down.  In the past
this has indicated that the clock went backwards (which confuses the
ruptime / rwho stuff).  What I usually do is log into the console, go
into single user and umount the filesystems before destroying the DOMU
(or if I am luckly a reboot, but that doesn't always work).  Upon doing
a "umount -a" the following was printed on the console:

[ 175409.0295886] WARNING: lwp 8442 (umount): negative runtime: (-1 + 0x857d0fb35b7fa2d0/2^64) sec
[ 175409.0295886] WARNING: pid 8442 (umount): negative runtime; monotonic clock has gone backwards

Before I did any of that I did a date and noticed that the clock was
about 1 hour behind.  I personally don't think that this could have been
due to anything gradually changing with the clock.



-- 
Brad Spencer - brad%anduin.eldar.org@localhost - KC8VKS - http://anduin.eldar.org