Hi,

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[1]
- HA stuff - and they make kernel panic[2] on Linux with 'b'[3] (immediate
reboot the system without syncing or unmounting them) or 'c'
(performing a kexec reboot in order to take a crashdump) under
some conditions.

[1] http://bit.ly/2IvFD9A
[2] https://fedoraproject.org/wiki/QA/Sysrq
[3] 
https://github.com/ClusterLabs/pacemaker/blob/edd67444e967a0c58a96aab1748b378eec3b40f9/lib/common/watchdog.c#L132

Jiri

Reply via email to