So, it looks like the latest version from the same ppa:cascardo/kdump2 should be working much better now, handling that specific situation from a new install containing crashkernel=196M. I tested both upgrade paths from older kdump-tools or new installs, and they are working fine starting with either no crashkernel parameter, that specific value of 196M or a different value, like 320M. In the first and second cases, we ended up with the new default value. On the third case, the user- configured value was kept.
Version is 1:1.6.7-4ubuntu1+cascardo6. Regards. Cascardo. -- 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
