[Kernel-packages] [Bug 2056231] Re: Error when installing nvidia-utils-535: "Invalid cross-device link"
Seeing some strange "Device or resource busy" errors on the /usr/bin/nvidia-debugdump file, seemingly due to Nvidia lossage. Closing as likely unrelated to the packaging. ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2056231 Title: Error when installing nvidia-utils-535: "Invalid cross-device link" Status in nvidia-graphics-drivers-535 package in Ubuntu: Invalid Bug description: This concerns nvidia-utils-535 (535.161.07-0ubuntu3) in Ubuntu noble. I had already installed nvidia-cuda-toolkit, and then... # apt-get install nvidia-utils-535 Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: nvidia-driver-535 The following NEW packages will be installed: nvidia-utils-535 0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded. Need to get 405 kB of archives. After this operation, 1157 kB of additional disk space will be used. Get:1 http://apt.example.com/ubuntu noble/restricted amd64 nvidia-utils-535 amd64 535.161.07-0ubuntu3 [405 kB] Fetched 405 kB in 0s (2693 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package nvidia-utils-535. (Reading database ... 51672 files and directories currently installed.) Preparing to unpack .../nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb ... Unpacking nvidia-utils-535 (535.161.07-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb (--unpack): unable to make backup link of './usr/bin/nvidia-debugdump' before installing new version: Invalid cross-device link dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2056231/+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 2056231] [NEW] Error when installing nvidia-utils-535: "Invalid cross-device link"
Public bug reported: This concerns nvidia-utils-535 (535.161.07-0ubuntu3) in Ubuntu noble. I had already installed nvidia-cuda-toolkit, and then... # apt-get install nvidia-utils-535 Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: nvidia-driver-535 The following NEW packages will be installed: nvidia-utils-535 0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded. Need to get 405 kB of archives. After this operation, 1157 kB of additional disk space will be used. Get:1 http://apt.example.com/ubuntu noble/restricted amd64 nvidia-utils-535 amd64 535.161.07-0ubuntu3 [405 kB] Fetched 405 kB in 0s (2693 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package nvidia-utils-535. (Reading database ... 51672 files and directories currently installed.) Preparing to unpack .../nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb ... Unpacking nvidia-utils-535 (535.161.07-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb (--unpack): unable to make backup link of './usr/bin/nvidia-debugdump' before installing new version: Invalid cross-device link dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2056231 Title: Error when installing nvidia-utils-535: "Invalid cross-device link" Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: This concerns nvidia-utils-535 (535.161.07-0ubuntu3) in Ubuntu noble. I had already installed nvidia-cuda-toolkit, and then... # apt-get install nvidia-utils-535 Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: nvidia-driver-535 The following NEW packages will be installed: nvidia-utils-535 0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded. Need to get 405 kB of archives. After this operation, 1157 kB of additional disk space will be used. Get:1 http://apt.example.com/ubuntu noble/restricted amd64 nvidia-utils-535 amd64 535.161.07-0ubuntu3 [405 kB] Fetched 405 kB in 0s (2693 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package nvidia-utils-535. (Reading database ... 51672 files and directories currently installed.) Preparing to unpack .../nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb ... Unpacking nvidia-utils-535 (535.161.07-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb (--unpack): unable to make backup link of './usr/bin/nvidia-debugdump' before installing new version: Invalid cross-device link dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/nvidia-utils-535_535.161.07-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2056231/+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 1722027] [NEW] Removing kernel packages leads to initrd regens, reboot-required
Public bug reported: This concerns linux-base 4.0ubuntu1 in Ubuntu Xenial. Removing Linux kernel packages from the system leads to initrd generation and causes /var/run/reboot-required to appear. Neither of these side effects should occur if only kernel packages older than the running one are removed, a common operation in system maintenance. Below is a terminal session illustrating the problem. Note the update- initramfs lines indicating that an initrd is being (re)generated. The removal process paused for a few seconds at these lines, because generating an initrd is somewhat disk- and CPU-intensive. (Look closely at the versions of the initrd that are generated---the system is refreshing initrd files for the kernel versions that are being removed!) Terminal log begins # ls /var/run/reboot-required ls: cannot access '/var/run/reboot-required': No such file or directory # apt-get --purge autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-83* linux-headers-4.4.0-83-generic* linux-headers-4.4.0-87* linux-headers-4.4.0-87-generic* linux-headers-4.4.0-89* linux-headers-4.4.0-89-generic* linux-headers-4.4.0-91* linux-headers-4.4.0-91-generic* linux-image-4.4.0-83-generic* linux-image-4.4.0-87-generic* linux-image-4.4.0-89-generic* linux-image-4.4.0-91-generic* linux-image-extra-4.4.0-83-generic* linux-image-extra-4.4.0-87-generic* linux-image-extra-4.4.0-89-generic* linux-image-extra-4.4.0-91-generic* 0 upgraded, 0 newly installed, 16 to remove and 0 not upgraded. After this operation, 1,188 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 353048 files and directories currently installed.) Removing linux-headers-4.4.0-83-generic (4.4.0-83.106) ... Removing linux-headers-4.4.0-83 (4.4.0-83.106) ... Removing linux-headers-4.4.0-87-generic (4.4.0-87.110) ... Removing linux-headers-4.4.0-87 (4.4.0-87.110) ... Removing linux-headers-4.4.0-89-generic (4.4.0-89.112) ... Removing linux-headers-4.4.0-89 (4.4.0-89.112) ... Removing linux-headers-4.4.0-91-generic (4.4.0-91.114) ... Removing linux-headers-4.4.0-91 (4.4.0-91.114) ... Removing linux-image-extra-4.4.0-83-generic (4.4.0-83.106) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.4.0-96-generic Found initrd image: /boot/initrd.img-4.4.0-96-generic Found linux image: /boot/vmlinuz-4.4.0-93-generic Found initrd image: /boot/initrd.img-4.4.0-93-generic Found linux image: /boot/vmlinuz-4.4.0-92-generic Found initrd image: /boot/initrd.img-4.4.0-92-generic Found linux image: /boot/vmlinuz-4.4.0-91-generic Found initrd image: /boot/initrd.img-4.4.0-91-generic Found linux image: /boot/vmlinuz-4.4.0-89-generic Found initrd image: /boot/initrd.img-4.4.0-89-generic Found linux image: /boot/vmlinuz-4.4.0-87-generic Found initrd image: /boot/initrd.img-4.4.0-87-generic Found linux image: /boot/vmlinuz-4.4.0-83-generic Found initrd image: /boot/initrd.img-4.4.0-83-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin done Purging configuration files for linux-image-extra-4.4.0-83-generic (4.4.0-83.106) ... Removing linux-image-4.4.0-83-generic (4.4.0-83.106) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic update-initramfs: Deleting /boot/initrd.img-4.4.0-83-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic Generating grub configuration file ... Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Found linux image: /boot/vmlinuz-4.4.0-96-generic Found initrd image: /boot/initrd.img-4.4.0-96-generic Found linux image: /boot/vmlinuz-4.4.0-93-generic Found initrd image: /boot/initrd.img-4.4.0-93-generic Found linux image: /boot/vmlinuz-4.4.0-92-generic Found initrd image: /boot/initrd.img-4.4.0-92-generic Found linux image: /boot/vmlinuz-4.4.0-91-generic Found initrd image: /boot/initrd.img-4.4.0-91-generic Found
[Kernel-packages] [Bug 1636701] Re: Removing kernel package triggers DKMS build
I should point out, the update-initramfs invocations should also not be happening for kernel packages being removed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1636701 Title: Removing kernel package triggers DKMS build Status in dkms package in Ubuntu: New Bug description: I'm filing this against dkms 2.2.0.3-2ubuntu11.2 in Ubuntu Xenial, although the issue may come down to a different package. I issued an "apt-get --purge autoremove" command to clear out some old kernel packages, and the command took several minutes to complete due to kernel module builds taking place during the process. Obviously, no builds should be occurring, because the associated kernels are being removed! Here is the terminal log of the command. Note the "run-parts: executing /etc/kernel/postinst.d/dkms ..." lines: # apt-get --purge autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-extra-4.4.0-21-generic* linux-image-extra-4.4.0-22-generic* linux-image-extra-4.4.0-24-generic* linux-image-extra-4.4.0-28-generic* snap-confine* ubuntu-core-launcher* 0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded. After this operation, 648 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 413863 files and directories currently installed.) Removing linux-image-extra-4.4.0-21-generic (4.4.0-21.37) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic update-initramfs: Generating /boot/initrd.img-4.4.0-21-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-45-generic Found initrd image: /boot/initrd.img-4.4.0-45-generic Found linux image: /boot/vmlinuz-4.4.0-43-generic Found initrd image: /boot/initrd.img-4.4.0-43-generic Found linux image: /boot/vmlinuz-4.4.0-28-generic Found initrd image: /boot/initrd.img-4.4.0-28-generic Found linux image: /boot/vmlinuz-4.4.0-24-generic Found initrd image: /boot/initrd.img-4.4.0-24-generic Found linux image: /boot/vmlinuz-4.4.0-22-generic Found initrd image: /boot/initrd.img-4.4.0-22-generic Found linux image: /boot/vmlinuz-4.4.0-21-generic Found initrd image: /boot/initrd.img-4.4.0-21-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin Setting default keymap configuration: model = pc104 layout = us variant = dvorak option = Unknown keyboard scan code 0x54 Unknown keyboard scan code 0x65 Unknown keyboard scan code 0x7f Unknown keyboard scan code 0x54 Unknown keyboard scan code 0x65 Unknown keyboard scan code 0x7f Unknown keyboard scan code 0x54 Unknown keyboard scan code 0x65 Unknown keyboard scan code 0x7f done Purging configuration files for linux-image-extra-4.4.0-21-generic (4.4.0-21.37) ... Removing linux-image-extra-4.4.0-22-generic (4.4.0-22.40) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic update-initramfs: Generating /boot/initrd.img-4.4.0-22-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-45-generic Found initrd image: /boot/initrd.img-4.4.0-45-generic Found linux image: /boot/vmlinuz-4.4.0-43-generic Found initrd image: /boot/initrd.img-4.4.0-43-generic Found linux image:
[Kernel-packages] [Bug 1636701] [NEW] Removing kernel package triggers DKMS build
Public bug reported: I'm filing this against dkms 2.2.0.3-2ubuntu11.2 in Ubuntu Xenial, although the issue may come down to a different package. I issued an "apt-get --purge autoremove" command to clear out some old kernel packages, and the command took several minutes to complete due to kernel module builds taking place during the process. Obviously, no builds should be occurring, because the associated kernels are being removed! Here is the terminal log of the command. Note the "run-parts: executing /etc/kernel/postinst.d/dkms ..." lines: # apt-get --purge autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-extra-4.4.0-21-generic* linux-image-extra-4.4.0-22-generic* linux-image-extra-4.4.0-24-generic* linux-image-extra-4.4.0-28-generic* snap-confine* ubuntu-core-launcher* 0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded. After this operation, 648 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 413863 files and directories currently installed.) Removing linux-image-extra-4.4.0-21-generic (4.4.0-21.37) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic update-initramfs: Generating /boot/initrd.img-4.4.0-21-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-21-generic /boot/vmlinuz-4.4.0-21-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-45-generic Found initrd image: /boot/initrd.img-4.4.0-45-generic Found linux image: /boot/vmlinuz-4.4.0-43-generic Found initrd image: /boot/initrd.img-4.4.0-43-generic Found linux image: /boot/vmlinuz-4.4.0-28-generic Found initrd image: /boot/initrd.img-4.4.0-28-generic Found linux image: /boot/vmlinuz-4.4.0-24-generic Found initrd image: /boot/initrd.img-4.4.0-24-generic Found linux image: /boot/vmlinuz-4.4.0-22-generic Found initrd image: /boot/initrd.img-4.4.0-22-generic Found linux image: /boot/vmlinuz-4.4.0-21-generic Found initrd image: /boot/initrd.img-4.4.0-21-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin Setting default keymap configuration: model = pc104 layout = us variant = dvorak option = Unknown keyboard scan code 0x54 Unknown keyboard scan code 0x65 Unknown keyboard scan code 0x7f Unknown keyboard scan code 0x54 Unknown keyboard scan code 0x65 Unknown keyboard scan code 0x7f Unknown keyboard scan code 0x54 Unknown keyboard scan code 0x65 Unknown keyboard scan code 0x7f done Purging configuration files for linux-image-extra-4.4.0-21-generic (4.4.0-21.37) ... Removing linux-image-extra-4.4.0-22-generic (4.4.0-22.40) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic update-initramfs: Generating /boot/initrd.img-4.4.0-22-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-22-generic /boot/vmlinuz-4.4.0-22-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.4.0-45-generic Found initrd image: /boot/initrd.img-4.4.0-45-generic Found linux image: /boot/vmlinuz-4.4.0-43-generic Found initrd image: /boot/initrd.img-4.4.0-43-generic Found linux image: /boot/vmlinuz-4.4.0-28-generic Found initrd image: /boot/initrd.img-4.4.0-28-generic Found linux image: /boot/vmlinuz-4.4.0-24-generic Found initrd image: /boot/initrd.img-4.4.0-24-generic Found linux image: /boot/vmlinuz-4.4.0-22-generic Found initrd image: /boot/initrd.img-4.4.0-22-generic Found linux image: /boot/vmlinuz-4.4.0-21-generic Found initrd image: /boot/initrd.img-4.4.0-21-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin Setting default keymap configuration:
[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
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
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
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
