Re: finding cause of reboot

On Fri, Oct 17, 2025 at 7:24 AM void <void@f-m.fm> wrote:

> Hi,
>
> On Thu, Oct 16, 2025 at 08:12:10AM -0600, Alan Somers wrote:
>
> >to make core dumps.  I suggest forcing a crash with
> >"sysctl debug.kdb.panic=1" while you watch the screen to see what happens.
>
> Not sure what this would do, apart from crash the machine immediately.
> The problem, when it happens, is it's like power reset.
>

I meant that you should do that just to check that core dumps are working.
If your dump device were misconfigured, for example, then a kernel panic
would lead to a reboot, looking much like a power reset.


>
> Ideally what I guess needs to happen is that the problem (whatever is
> causing it) needs to crash to debugger or and/or make a crash dump
> before completely exiting. Do you think enabling WITNESS and friends
> may help?
> --
>

That's a good idea, if it's really the dump device that's a problem.  But
you don't need WITNESS.  Simply enabling ddb should be sufficient.  You'll
have to configure /etc/ddb.conf to break to debugger rather than dump core.