Comment 10 for bug 1908090
Revision history for this message
| Tyler Stachecki (tstachecki) wrote Re: Default 192MB crashkernel reservation is never enough (kdump fails on 20.04) | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This really, really should be raised.
Not setting the default higher risks a loss of coredumps from production systems due to memory exhaustion when the host boots the kdump kernel. You would think that something like that was tested in all cases, but I did not and just got bit on what was fortunately a toy system...
If you really want to be conservative, you could even say kdump with systems <= 2GiB of RAM or something should only use 192M still (though as per Trent's observations -- it seems like the floor needs to be raised, period? or initrd needs to go on a diet?)