hm.. you're right. I was tracking down a different issue which had the following backtrace:
[ 10.701967] Call trace: [ 10.704415] ata_host_activate+0x160/0x170 [ 10.708518] ahci_host_activate+0x170/0x1e0 [ 10.712711] ahci_init_one+0x898/0xd74 [ahci] [ 10.717116] local_pci_probe+0x4c/0xc0 [ 10.720883] work_for_cpu_fn+0x28/0x40 [ 10.724635] process_one_work+0x20c/0x4d0 [ 10.728647] worker_thread+0x250/0x564 [ 10.732393] kthread+0x134/0x140 [ 10.735616] ret_from_fork+0x10/0x18 Reverting the bisect-id'd commit from upstream 5.13-rc1 does fix this issue for me, but perhaps it was already fixed in v5.13 final. I *can* reproduce the backtrace here w/ the archive 5.13.0-16, but I can not with a locally built 5.13-rc1 (w/ the above patch reverted). The fact that you can reproduce with 5.13-rc1 makes me wonder if the issue maybe toolchain related. I'm building in a hirsute environment. I'll try building 5.13.0-16 in a hirsute environment to test that theory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942633 Title: Can not boot impish in Cavium ThunderX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
