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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Confirmed Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x431f0a11] [ 0.000000] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [ 0.000000] Machine model: Cavium ThunderX CN88XX board .... [ 139.896752] raid6: .... xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571] 8regs : 2432 MB/sec [ 140.149834] 32regs : 2687 MB/sec [ 140.212202] arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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
