@xnox: yes, we usually respin before release with only hot-fixes on top. The other patch you mentioned was just applied in Groovy and pushed.
-- 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/1899519 Title: booting linux-generic-lpae armhf kernel under qemu results in relocation out of range, and thus no modules can be loaded Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Groovy armhf LPAE kernel fails to load kmods (and thus fail to boot). [Fix] Enable CONFIG_ARM_MODULE_PLTS for armhf [Regression potential] Quoting the arch/arm/Kconfig: "This [option] allows modules to be allocated in the generic vmalloc area after the dedicated module memory area has been exhausted. The modules will use slightly more memory, but after rounding up to page size, the actual memory footprint is usually the same. Disabling this is usually safe for small single-platform configurations. " --- qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1 -drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel ./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic- lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.8.0-21-generic-lpae (buildd@bos02-arm64-041) (gcc (Ubuntu 10.2.0-11ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #22-Ubuntu SMP Fri Oct 2 12:30:15 UTC 2020 (Ubuntu 5.8.0-21.22-generic-lpae 5.8.13) [ 0.000000] CPU: ARMv7 Processor [412fc0f1] revision 1 (ARMv7), cr=30c5387d Starting version 246.6-1ubuntu1 [ 16.753306] gpio_keys: section 4 reloc 29 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f23c -> 0xc10a90ec) Begin: Loading essential drivers ... [ 22.799409] linear: section 4 reloc 43 sym '__stack_chk_fail': relocation 28 out of range (0xbf0195e8 -> 0xc10a1dd8) [ 23.000670] multipath: section 4 reloc 31 sym '__stack_chk_fail': relocation 28 out of range (0xbf021268 -> 0xc10a1dd8) [ 23.227437] raid0: section 4 reloc 53 sym '__stack_chk_fail': relocation 28 out of range (0xbf02a548 -> 0xc10a1dd8) [ 23.460764] raid1: section 4 reloc 18 sym '_cond_resched': relocation 28 out of range (0xbf035390 -> 0xc10a3b4c) [ 28.311563] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 31.866657] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.632259] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) [ 35.852163] raid10: section 4 reloc 21 sym '__stack_chk_fail': relocation 28 out of range (0xbf00b404 -> 0xc10a1dd8) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 41.265330] libcrc32c: section 4 reloc 9 sym '__stack_chk_fail': relocation 28 out of range (0xbf0030b8 -> 0xc10a1dd8) (initramfs) cat /proc/modules (initramfs) modprobe virtio_blk [ 121.814904] virtio_blk: section 4 reloc 3 sym '_raw_spin_lock_irqsave': relocation 28 out of range (0xbf003050 -> 0xc10a90ec) (initramfs) cat /proc/modules (initramfs) Are we miss-building the kernel and/or modules? Or am I miss-launching the VM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899519/+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
