Hello, After investigating the issue, it turns out that an adequate solution is not possible without sensible modification to the kernel.
As explained before, the kernel allows for the definition of a vm_free_kbytes which is above the size of the total memory available. This parameter is enable very early during the boot phase and cannot easily be disabled. kdump is not at fault here since it doesn't even get a chance to run prior to when the OOM starts killing processes. The only workaround is to remove the definition of vm.vm_free_kbytes from the /etc/sysctl.conf file so the kernel dump may proceed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528101 Title: ISST-LTE: kdump failed: second kernel booting hangs after /scripts /init-bottom when large min_free_kbytes value being set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1528101/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
