Paul de Weerd:
> Indeed, `sysctl kern.securelevel=-1` allows entering DDB with `sysctl
> ddb.trigger=1`. (Yes, I am logged in over serial, and that works
> well). That was not clear from the ddb manpage, nor from the
> securelevel manpage
It's in sysctl(2):
DBCTL_TRIGGER (ddb.trigger)
When DBCTL_CONSOLE is set, writing to DBCTL_TRIGGER causes the
system to enter ddb(4). When running with a securelevel(7)
greater than 0, the process writing to this variable must be
running on the console in order to enter ddb(4).
> --- ddb.4 22 Dec 2022 19:53:22 -0000 1.105
> +++ ddb.4 30 May 2023 06:34:19 -0000
> @@ -46,7 +46,9 @@ is invoked upon a kernel panic when the
> is set to 1.
> It may be invoked from the console when the sysctl
> .Va ddb.console
> -is set to 1, using any of the following methods:
> +is set to 1 and
> +.Va kern.securelevel
> +is set to 0 or -1, using any of the following methods:
But your problem appears to be that you are invoking it not from
the console.
--
Christian "naddy" Weisgerber na...@mips.inka.de
