Hello,
The situation in this context is that the modification of
vm.min_free_kbytes has a negative impact on the boot sequence of the
kexec kernel (the kernel that allows for the capture of the kernel
dump).
The output of the console that you provide clearly shows that the kdump
sequence hasn't even started to execute so kexec-tools is not the
culprit here. Now I agree that kernel parameter modifications made for
normal execution of the kernel should not impair the execution of the
kexec kernel when this one needs to run.
So we need to find a solution that will let us boot the kexec kernel
with the default value for vm.min_free_kbytes and not the modified one.
I will look into that.
** Changed in: kexec-tools (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
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
