------- Comment From ru...@us.ibm.com 2016-03-28 16:01 EDT------- Minor changes to the kernel handling of user_min_free_kbytes appears to be the ideal solution here since it would have benefits outside of the kdump environment. Currently, it appears that it is too easy to manually set a completely inappropriate value. Elsewhere, the value is capped at either 65536 or 5% of lowmem, but it appears that the user provided value is not run through the same sanity checks (see init_per_zone_wmark_min() as an example).
-- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
