Re: finding cause of reboot

If sysctl debug.debugger_on_panic: 1 is set that SHOULD drop you to the 
debugger on a panic.

Obviously if the cause is that Power Good disappeared from the power 
supply, or an /unchecked /(on a non-ECC machine) memory fault caused the 
processor to effectively reset then it won't.

This assumes the debug options are in the kernel you are running; 
GENERIC (last I checked) does.

https://man.freebsd.org/cgi/man.cgi?ddb(4)

On 10/17/2025 9:24 AM, void 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.
>
> 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?
-- 
Karl Denninger
karl@denninger.net
/The Market Ticker/
/[S/MIME encrypted email preferred]/