Public bug reported: [Impact] kdump support isn't usable on HiSilicon D05 systems. This previously worked in bionic.
[Test Case] sudo apt install linux-crashdump echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=512M"' | \ sudo tee /etc/default/grub.d/kdump-tools.cfg sudo update-grub sudo reboot echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 2 upstream patch series are required to fix this: https://www.mail-archive.com/linux-efi@vger.kernel.org/msg10328.html Which provides an EFI facility consumed by: https://lkml.org/lkml/2018/9/21/1066 There were also some follow-on fixes to deal with ARM-specific problems associated with this usage: https://www.spinics.net/lists/arm-kernel/msg685751.html [Regression Risk] The EFI changes are in architecture independent code where they add a new table and an API for adding regions to that table. However, this API is only used by the gic-v3-its driver, which is ARM-specific. On other architectures, this will be an empty table. It's possible that there is a bug bug in the table creation code that could cause regressions on other architectures, which would likely be seen in the form of a boot time error message (Failed to install memreserve config table). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New -- 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/1806766 Title: [Regression] crashkernel fails on HiSilicon D05 Status in linux package in Ubuntu: New Status in linux source package in Cosmic: New Status in linux source package in Disco: New Bug description: [Impact] kdump support isn't usable on HiSilicon D05 systems. This previously worked in bionic. [Test Case] sudo apt install linux-crashdump echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=512M"' | \ sudo tee /etc/default/grub.d/kdump-tools.cfg sudo update-grub sudo reboot echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 2 upstream patch series are required to fix this: https://www.mail-archive.com/linux-efi@vger.kernel.org/msg10328.html Which provides an EFI facility consumed by: https://lkml.org/lkml/2018/9/21/1066 There were also some follow-on fixes to deal with ARM-specific problems associated with this usage: https://www.spinics.net/lists/arm-kernel/msg685751.html [Regression Risk] The EFI changes are in architecture independent code where they add a new table and an API for adding regions to that table. However, this API is only used by the gic-v3-its driver, which is ARM-specific. On other architectures, this will be an empty table. It's possible that there is a bug bug in the table creation code that could cause regressions on other architectures, which would likely be seen in the form of a boot time error message (Failed to install memreserve config table). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806766/+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
