The sysrq mechanism allows someone with physical access to the system to
easily cause it to boot by just pressing some keys. That's why the sysrq
default allows only very few commands to be issued. kdump is for real
crashes. kdump testing may require using the sysrq-trigger mechanism,
but that could just as well write to /proc/sys/kernel/sysrq before
causing the crash. In fact, that's just what kdump-tools autopkgtest
does.
echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger
So, not a bug here.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Cosmic)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793369
Title:
Ubuntu18.10:ppc64:s390x - Sysrq trigger disabled when writing to /proc
/sysrq-trigger
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1793369/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
