There should be no difference between using di or the new installer, unless there is something the installer is doing that is causing this. If you remove the crashkernel line from zipl.conf and run dpkg- reconfigure kdump-tools, it should add the new configuration value. Otherwise, it will keep whatever other value is there. The only exception is when you are upgrading from an older version of kdump-tools and it finds the value that old kdump-tools would put in there.
There is a chance I am misreading the code from s390-tools package (the one with zipl). It used to add the crashkernel parameter there, but only when upgrading from versions pre-Xenial. I even tested that on a new system, when removing and reinstalling s390-tools, there was no crashkernel line in there. We are trying to reproduce this locally and will investigate what may be causing this. One other option would be to also replace that specific value. I would rather not do it unless really necessary, because otherwise we might replace a value put there by a user. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
