On Sun, Jun 11, 2023 at 07:08:47PM +0200, Why 42? The lists account. wrote:
>
> On Wed, Jun 07, 2023 at 03:50:29PM +0300, Vitaliy Makkoveev wrote:
> > > Please, share your dvmrpd.conf.
> > >
> >
> > Also, you could try to use ktrace to provide some additional info.
>
> Hi,
>
> Thanks for responding, the system is some 30Km away and, er, crashed.
> But maybe I will get there tomorrow. I wasn't able to get it to react to
> input from the remote KVM system that I was using,
>
> AFAICR, the dvmrpd.conf just contained a copy of the file from examples,
> with the interface names changed to "em0" and "ure0" i.e. the two "up"
> interfaces on the system (ure being a T-Link USB-Ethernet adaptor).
>
> Forgive my ignorance, but does this matter? I mean the error looks (to
> me) like an attempt to catch an unexpected set of cirumstances i.e.
>
> kernel diagnostic assertion "ident == &nowake || timo ||
> _kernel_lock_held()" failed
>
> It seems as if none of those three things were true, therefore the
> assertion failed, so we just need to know why it was written in the first
> place and the meaning of those clauses, if you see what I mean?
>
> Cheers,
> Robb.
>
> P.S. I was starting the daemon manually via a terminal window, just as
> you suggested.
In general, if a developer asks for information on a setup, it's with
good reason. Details do matter. Just give the information.
-Otto
