Public bug reported:
[Impact]
The fix for LP: #1806766 has the issue that the persistent memory reservations
for the GICv3 LPI tables may have been allocated an overwritten by the time we
get to reserving them. This can continue to break kdump in certain conditions.
[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]
582a32e708823 efi/arm: Revert "Defer persistent reservations until after
paging_init()"
8a5b403d71aff arm64, mm, efi: Account for GICv3 LPI tables in static memblock
reserve table
[Regression Risk]
The change in reserved regions only impacts arm64.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: In Progress
** Affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: In Progress
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Status: In Progress
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816425
Title:
Use memblock quirk instead of delayed allocation for GICv3 LPI tables
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816425/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
