IIUC we can panic kernel via writting to 'ddb.trigger' and
if we have 'ddb.panic=0' it would reboot.
But IIUC we are not not able to control what would happen
during this kernel panic in non-interactive mode, am I right?
I am asking because I'm working on porting corosync/pacemaker
- HA stuff - and they make kernel panic on Linux with 'b' (immediate
reboot the system without syncing or unmounting them) or 'c'
(performing a kexec reboot in order to take a crashdump) under