[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: grub (Ubuntu Precise) Status: Confirmed => Won't 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in grub package in Ubuntu: Fix Released Status in kexec-tools package in Ubuntu: Fix Released Status in grub source package in Precise: Won't Fix Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x "/usr/bin/makedumpfile" ] && [ -x "/sbin/kexec" ]; then GRUB_CMDLINE_EXTRA="$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M" fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent "out of memory" kernel panic. (A side effect of the "double crash" is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
I'd just like to report in that I couldn't get it to work, it only did after raising the limit to 256M on a server with 256GB of memory. -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in grub package in Ubuntu: Fix Released Status in kexec-tools package in Ubuntu: Fix Released Status in grub source package in Precise: Confirmed Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
** No longer affects: grub (Ubuntu Raring) ** No longer affects: grub (Ubuntu Quantal) ** No longer affects: grub (Ubuntu Saucy) ** Changed in: grub (Ubuntu Precise) Assignee: Chris J Arges (arges) = (unassigned) ** Changed in: grub (Ubuntu Precise) Status: In Progress = Confirmed ** Changed in: grub (Ubuntu Precise) Importance: Medium = Undecided -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: Fix Released Status in “kexec-tools” package in Ubuntu: Fix Released Status in “grub” source package in Precise: Confirmed Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
Please keep in mind the 128Mb is some kind of catchall for defined when memory sizes did not go much higher than 16Gb. I will inquire in the ML that covers makedumpfile to see if there is a way to come up with an estimate of the required memory and will report back. In the meantime, I don't see any issue with having to setup the value manually for servers that have large amount of memory. -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: Fix Released Status in “kexec-tools” package in Ubuntu: Fix Released Status in “grub” source package in Precise: In Progress Status in “grub” source package in Quantal: In Progress Status in “grub” source package in Raring: In Progress Status in “grub” source package in Saucy: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
RFE Let there be a separate tool/command that would provide an estimate of the memory required for the localhost. -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: Fix Released Status in “kexec-tools” package in Ubuntu: Fix Released Status in “grub” source package in Precise: In Progress Status in “grub” source package in Quantal: In Progress Status in “grub” source package in Raring: In Progress Status in “grub” source package in Saucy: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
Bryan: Are you saying 256MB was needed in order for the crash kernel to boot, that 128MB was not enough? (I'm not sure that there is any advantage to reserving more memory than needed, aside from the kernel one day growing to need 129MB) -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: Fix Released Status in “kexec-tools” package in Ubuntu: Fix Released Status in “grub” source package in Precise: In Progress Status in “grub” source package in Quantal: In Progress Status in “grub” source package in Raring: In Progress Status in “grub” source package in Saucy: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
128MB didn't work 256MB did Nothing else was tested on this machine. -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: Fix Released Status in “kexec-tools” package in Ubuntu: Fix Released Status in “grub” source package in Precise: In Progress Status in “grub” source package in Quantal: In Progress Status in “grub” source package in Raring: In Progress Status in “grub” source package in Saucy: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
Ah, okay, that's an issue. Not only do we not have an easy way of measuring how much memory a kernel needs to boot, we don't know how that requirement varies depending on the system configuration... -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: Fix Released Status in “kexec-tools” package in Ubuntu: Fix Released Status in “grub” source package in Precise: In Progress Status in “grub” source package in Quantal: In Progress Status in “grub” source package in Raring: In Progress Status in “grub” source package in Saucy: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
** Also affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: kexec-tools (Ubuntu) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: kexec-tools (Ubuntu) Importance: Undecided = Medium ** Changed in: kexec-tools (Ubuntu) Status: New = In Progress -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: In Progress Status in “kexec-tools” package in Ubuntu: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
Pushed changes into kexec-tools trusty. Let's test these changes first, then modify the grub packages in earlier releases via SRU if trusty is working fine. -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: In Progress Status in “kexec-tools” package in Ubuntu: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
** Branch linked: lp:ubuntu/trusty-proposed/kexec-tools -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: In Progress Status in “kexec-tools” package in Ubuntu: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
This bug was fixed in the package kexec-tools - 1:2.0.3-4ubuntu3 --- kexec-tools (1:2.0.3-4ubuntu3) trusty; urgency=low * Increase memory parameter crashkernel command line to 128M to avoid OOM kernel panic. (LP: #785394) -- Chris J Arges chris.j.ar...@ubuntu.com Wed, 18 Dec 2013 10:54:08 -0600 ** Changed in: kexec-tools (Ubuntu) Status: In Progress = Fix Released -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: In Progress Status in “kexec-tools” package in Ubuntu: Fix Released Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
** Also affects: grub2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Trusty) Importance: Undecided Status: Confirmed ** Also affects: kexec-tools (Ubuntu Trusty) Importance: Medium Assignee: Andy Whitcroft (apw) Status: In Progress ** Also affects: grub2 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Raring) Importance: Undecided Status: New ** No longer affects: grub2 (Ubuntu) ** No longer affects: grub2 (Ubuntu Precise) ** No longer affects: grub2 (Ubuntu Raring) ** No longer affects: grub2 (Ubuntu Quantal) ** No longer affects: grub2 (Ubuntu Saucy) ** No longer affects: grub2 (Ubuntu Trusty) -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “kexec-tools” package in Ubuntu: In Progress Status in “kexec-tools” source package in Precise: New Status in “kexec-tools” source package in Quantal: New Status in “kexec-tools” source package in Raring: New Status in “kexec-tools” source package in Saucy: New Status in “kexec-tools” source package in Trusty: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
** Also affects: grub (Ubuntu) Importance: Undecided Status: New ** No longer affects: kexec-tools (Ubuntu) ** No longer affects: kexec-tools (Ubuntu Precise) ** No longer affects: kexec-tools (Ubuntu Quantal) ** No longer affects: kexec-tools (Ubuntu Raring) ** No longer affects: kexec-tools (Ubuntu Saucy) ** No longer affects: kexec-tools (Ubuntu Trusty) ** Changed in: grub (Ubuntu) Assignee: (unassigned) = Chris J Arges (arges) ** Changed in: grub (Ubuntu) Importance: Undecided = Medium ** Changed in: grub (Ubuntu) Status: New = In Progress -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub” package in Ubuntu: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
I systematically change the setting on all my VMs to 128M as I have had repeated failure with 64M. I think that the default should be raised to 128Mb which is the default on Debian anyway. -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub2” package in Ubuntu: Confirmed Status in “kexec-tools” package in Ubuntu: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
Agreed. It's not clear that there is *any* standard Ubuntu kernel configuration that can boot in 64MB. And having that as a default is worse than useless, because the crash-kernel's OOM prevents the system from recovering automatically after a kernel crash. -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub2” package in Ubuntu: Confirmed Status in “kexec-tools” package in Ubuntu: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
@Daniel I'm wrong, not fixed in 13.04+ I ran some tests: @Chiluk first up vm images do only need 64 mb reserved: Trusty 512 MB (m1.tiny) image on OpenStack: allocted 64 MB of ram for crashdump and it worked. (dump size of 23 mb) Desktop images fail Trusty 2047 MB (Vagrant/Virtualbox desktop image) - allocated 64 MB of ram for crashdump and hung. Reran with 100MB for crashdump, worked (dump size of 32 mb) Is there any way to not be guessing here and generate the right number for the kernel you are using and modules that have been loaded? (In other words, get current kernel size and add percentage buffer). Per another private case we may have situations where 128 MB is not enough. If we can't auto-detect this (building upon chiluk's' comment), I would suggest something like (the numbers can change but I think we do need more levels): 1.5 GB of RAM: is it virtual kernel? then do 64 mb, if not do 128 mb 1.5 GB to 4 GB: everything do 192 mb 4 GB+: 256 mb 12 GB+: 512 mb (is there a point when we should stop?) -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub2” package in Ubuntu: Confirmed Status in “kexec-tools” package in Ubuntu: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
Bryan: Could you elaborate on how this issue appears to be fixed in 13.04? Was the memory reservation increased to 128MB, or is the kernel now capable of booting in 64MB? Given the lack of any updates here, I'm doubtful that any progress has been made at all. Dave: Have you tried crash-booting a *-virtual kernel in 64MB, experimentally? The possibility is interesting, but it should be more than just a guess. -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub2” package in Ubuntu: Confirmed Status in “kexec-tools” package in Ubuntu: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/785394/+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
[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
This appears to be fixed in 13.04+. Any chance we can get a fix backported to 12.04? If not, can we increase the memory by default? -- 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/785394 Title: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient Status in “grub2” package in Ubuntu: Confirmed Status in “kexec-tools” package in Ubuntu: In Progress Bug description: Binary package hint: grub-pc This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty. The /etc/grub.d/10_linux file contains this snippet: # add crashkernel option if we have the required tools if [ -x /usr/bin/makedumpfile ] [ -x /sbin/kexec ]; then GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:64M,2G-:128M fi I am on a system with 2GB of RAM (reported as 2038MB), and according to the kernel startup messages, 64MB is reserved for the crash kernel. Unfortunately, this does not appear to be enough memory for the regular Ubuntu kernel to boot. I am attaching a kernel log obtained via serial cable; it shows the initial boot, a crash in the kernel's video-driver-related code, the subsequent crashkernel boot, and then an apparent out of memory kernel panic. (A side effect of the double crash is that the system is left unresponsive, requiring a manual reset instead of rebooting itself automatically.) If I double the memory numbers in the crashkernel=... argument, so that the reservation is 128MB, the system correctly goes on to attempt a vmcore dump and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/785394/+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