The initial crashkernel size is just a default value - that was in the past a reasonable good value.
So it's not uncommon that one needs to increase the crashkernel size for a particular situation and setup. The default size is always a trade-off between reserving enough space for all possible situations and environments vs. not reserving and wasting too much space. But we already noticed that the default needs an increase nowadays, which was in general already addressed in LP#1877533. LP#1877533 is not done yet, since the approach is to do it in alignment with Debian. Nevertheless, I tend to mark this LP#1946463 as duplicate of LP#1877533 ... ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Summary changed: - Ubuntu20.04.3 default crashkernel size insufficient for kdump + Ubuntu 20.04.3 default crashkernel size insufficient for kdump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946463 Title: Ubuntu 20.04.3 default crashkernel size insufficient for kdump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1946463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs