Setting as Invalid for linux, as this is not a linux bug. Marking as
Confirmed for makedumpfile, where there is a chance this might be fixed.
However, I disagree with checking for a specific module on a specific
architecture to decide crashkernel size.
crashkernel size is a suggestion. Users are supposed to test that kdump
works with the size they are supposed to configure. We may need to
document that.
** Also affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Status: New => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Changed in: makedumpfile (Ubuntu Groovy)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877533
Title:
[20.10 FEAT] Increase the crashkernel setting if the root volume is
luks2-encrypted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
