[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- Comment From pt...@cn.ibm.com 2016-04-04 21:50 EDT--- (In reply to comment #42) > The documentation is not fixed and recommends the usage of 5% of your whole > memory as the min_free_kbyte is documented at: > > https://wiki.ubuntu.com/ppc64el/ > Recommendations#Min_free_kbytes_kernel_configuration Hi, On some situations, such as bug 139648, we have to use a large min_free_kbytes vaule to prevent oom killer being triggered when running stress tests. So looks like a large min_free_kbytes is needed. And I think this bug isn't a problem of min_free_kbytes too large. It is because that when performing kdump, the value is read from /etc/sysctl.conf. If we can change this (don't using min_free_kbytes of /etc/sysctl.conf), this bug can be fxied. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in 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 Status in kexec-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the
[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- Comment From pt...@cn.ibm.com 2016-03-28 21:29 EDT--- Hi, This bug only occurs when min_free_kbytes=312721 is written in /etc/sysctl.conf. If we didn't write it into /etc/sysctl.conf and just set it with "sysctl min_free_kbytes=312721", then this bug won't be triggered when triggering kdump. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in 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 Status in kexec-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the default min_free_kbytes value then kdump works just fine! == Comment: #14 - Hari Krishna Bathini - 2015-12-10 00:51:43 == (In reply to comment #13) > (In reply to comment #12) > > Is the issue only seen with sysctl configuration > > "vm.min_free_kbytes = 312721" ? > > > > Yes, I just found that if use the default min_free_kbytes value then kdump > works just fine! It is blocking kdump from utilising the memory
[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- 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 Kernel Packages, which is subscribed to kexec-tools in 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 Status in kexec-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the default min_free_kbytes value then kdump works just fine! == Comment: #14 - Hari Krishna Bathini - 2015-12-10 00:51:43 == (In reply to comment #13) > (In reply to comment #12) > > Is the issue only seen with sysctl
[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- Comment From carri...@us.ibm.com 2016-03-15 12:53 EDT--- (In reply to comment #33) > Yes, I have started to work on a possible solution. Do you have any update on the solution to this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in 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 Status in kexec-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the default min_free_kbytes value then kdump works just fine! == Comment: #14 - Hari Krishna Bathini - 2015-12-10 00:51:43 == (In reply to comment #13) > (In reply to comment #12) > > Is the issue only seen with sysctl configuration > > "vm.min_free_kbytes = 312721" ? > > > > Yes, I just found that if use the default min_free_kbytes value then kdump > works just fine! It is blocking kdump from utilising the memory needed to boot. So, crashkernel=768M with min_free_kbytes configured to 312721 translates to ~450 MB
[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- Comment From pt...@cn.ibm.com 2016-03-16 23:03 EDT--- (In reply to comment #35) > 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. Looks like kdump of ubuntu uses the default initrd of production kernel and it will read the /etc/sysctl.conf. I think we can add some code to figure which context is before trying to read it and don't use it when running kdump. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in 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 Status in kexec-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han
[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- Comment From carri...@us.ibm.com 2016-01-28 12:28 EDT--- (In reply to comment #31) > Hello, > > The context here is that your modification of vm.min_free_kbytes brings the > value of vm_free_kbytes above the available memory defined by the > crashkernel boot parameter. > > A definitive fix for this situation requires some non trivial development, > which will take time. > > I can only suggest for the time being to raise the value of crashkernel for > your system, in order to alleviate the problem until a definitive solution > is implemented. Hello, Canonical. Just for clarification, is this something you'll be working to fix? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in 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 Status in kexec-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the default min_free_kbytes value then kdump works just fine! == Comment: #14 - Hari Krishna Bathini
[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- Comment From nad...@us.ibm.com 2016-01-22 17:18 EDT--- Any update to this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in 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 Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the default min_free_kbytes value then kdump works just fine! == Comment: #14 - Hari Krishna Bathini - 2015-12-10 00:51:43 == (In reply to comment #13) > (In reply to comment #12) > > Is the issue only seen with sysctl configuration > > "vm.min_free_kbytes = 312721" ? > > > > Yes, I just found that if use the default min_free_kbytes value then kdump > works just fine! It is blocking kdump from utilising the memory needed to boot. So, crashkernel=768M with min_free_kbytes configured to 312721 translates to ~450 MB for second kernel boot (kdump) which doesn't seem to be sufficient for booting. How to handle this: 1. Reserve
[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- Comment From pt...@cn.ibm.com 2016-01-11 22:10 EDT--- This bug can be reproduced on 14.04.4. I'd like to change the version to 14.04.4. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in 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 Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the default min_free_kbytes value then kdump works just fine! == Comment: #14 - Hari Krishna Bathini - 2015-12-10 00:51:43 == (In reply to comment #13) > (In reply to comment #12) > > Is the issue only seen with sysctl configuration > > "vm.min_free_kbytes = 312721" ? > > > > Yes, I just found that if use the default min_free_kbytes value then kdump > works just fine! It is blocking kdump from utilising the memory needed to boot. So, crashkernel=768M with min_free_kbytes configured to 312721 translates to ~450 MB for second kernel boot (kdump) which doesn't seem
[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- Comment From pt...@cn.ibm.com 2016-01-11 20:55 EDT--- Hi, This problem occurs on the system which has been set a high vm.min_free_kbytes value in the /etc/sysctl.conf. On those systems, kdump will fail. The workaround is set the value each time by running 'sysctl'. This isn't convenient. We'd like to have a solution that the value of vm.min_free_kbytes in production system's /etc/sysctl.con doesn't affect running of kdump. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in 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 Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the default min_free_kbytes value then kdump works just fine! == Comment: #14 - Hari Krishna Bathini - 2015-12-10 00:51:43 == (In reply to comment #13) > (In reply to comment #12) > > Is the issue only seen with sysctl configuration > > "vm.min_free_kbytes = 312721" ? > > > > Yes, I just
[Kernel-packages] [Bug 1528101] Comment bridged from LTC Bugzilla
--- Comment From hepat...@in.ibm.com 2015-12-28 10:39 EDT--- Hi Launchpad, Can you please take a look and assign appropriate developer to solve this bug? Thanks for your support..! - Henish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in 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 Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han- 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the default min_free_kbytes value then kdump works just fine! == Comment: #14 - Hari Krishna Bathini - 2015-12-10 00:51:43 == (In reply to comment #13) > (In reply to comment #12) > > Is the issue only seen with sysctl configuration > > "vm.min_free_kbytes = 312721" ? > > > > Yes, I just found that if use the default min_free_kbytes value then kdump > works just fine! It is blocking kdump from utilising the memory needed to boot. So, crashkernel=768M with min_free_kbytes configured to 312721 translates to ~450 MB for second kernel boot (kdump) which doesn't seem to be