I've reported a Debian bug with the proposed fixes; the merge report has
the information about the approach used to deal with sysctl in kdump:
https://salsa.debian.org/debian/makedumpfile/-/merge_requests/2
Cheers,
Guilherme
** Bug watch added: Debian Bug tracker #961880
https://bugs.debian.
Thanks Dan for the report and Cascardo for finding the offender commit
that introduced this regression!
I think we have room for improvements here, my considerations are:
a) KDUMP_SYSCTL is a misleading name; it seems to be related with sysctls set
_when_ dumping, which is also an important thing
** Also affects: makedumpfile (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Focal)
Importance: Low
Status: Triaged
** Also affects: makedumpfile (
** Changed in: makedumpfile (Ubuntu)
Status: New => Triaged
** Changed in: makedumpfile (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845048
Title:
commit 9a77ef188b24742b595f69891b97d48dc997f5e2
Author: Louis Bouchard
Date: Thu Jan 29 16:03:04 2015 +0100
[debian] Fix panic_on_oops faulty handling
Signed-off-by: Louis Bouchard
diff --git a/debian/kdump-config b/debian/kdump-config
index 7ea26cab1c95..64489a74757f 100755
---
This was somehow removed between kdump-tools 1.5.5 and 1.5.9. I'll see
if I can pinpoint the exact version in history and try to find some
justification. But this is an old regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Also to clarify, manually unloading/reloading kdump doesn't set the
params properly:
ubuntu@makedumpfile-e:~$ grep . /proc/sys/kernel/panic_on_warn
0
ubuntu@makedumpfile-e:~$ sudo kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1 kernel.panic_o