Re: sysctl ddb.trigger

2023-05-30 Thread Christian Weisgerber
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

Re: sysctl ddb.trigger

2023-05-30 Thread Paul de Weerd
Thank you, Stuart, Sebastien and Aaron (and others, off-list). 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 (admittedly, I

Re: sysctl ddb.trigger

2023-05-29 Thread Stuart Henderson
On 2023-05-29, Sebastien Marie wrote: > On Mon, May 29, 2023 at 02:41:00PM +1000, Aaron Mason wrote: >> On Mon, May 29, 2023 at 4:08 AM Paul de Weerd wrote: >> > >> > (for the record, BREAK doesn't work either to enter ddb, I >> > guessed it was due to the USB-to-serial dongle I'm

Re: sysctl ddb.trigger

2023-05-28 Thread Sebastien Marie
> > pom# sysctl ddb.{console,panic} > > ddb.console=1 > > ddb.panic=1 > > pom# sysctl ddb.trigger=1 > > sysctl: ddb.trigger: Operation not supported by device > > > > Am I holding this thing wrong? According to ddb(4), the above should > &g

Re: sysctl ddb.trigger

2023-05-28 Thread Aaron Mason
trying > to figure out. > > While debugging, I thought I'd try to enter ddb, so I set ddb.console > to 1 in /etc/sysctl.conf and tried to write to ddb.trigger: > > pom# sysctl ddb.{console,panic} > ddb.console=1 > ddb.panic=1 > pom# sysctl ddb.trigger=1 > sysctl: ddb.t

sysctl ddb.trigger

2023-05-28 Thread Paul de Weerd
ddb.console to 1 in /etc/sysctl.conf and tried to write to ddb.trigger: pom# sysctl ddb.{console,panic} ddb.console=1 ddb.panic=1 pom# sysctl ddb.trigger=1 sysctl: ddb.trigger: Operation not supported by device Am I holding this thing wrong? According to ddb(4), the above should be sufficient