This one looks new to me. I don't see any clear error in the log, but I assume it's riscv specific. WARNING: core-image-ptest-tar-1.0-r0 do_testimage: Target didn't reach login banner in 1500 seconds (08/22/26 23:40:02) WARNING: core-image-ptest-tar-1.0-r0 do_testimage: Last 25 lines of login console (2983): Domain0 Region01 : 0x0000000080000000-0x000000008003ffff M: (F,R,X) S/U: () Domain0 Region02 : 0x0000000000100000-0x0000000000100fff M: (I,R,W) S/U: (R,W) Domain0 Region03 : 0x0000000010000000-0x0000000010000fff M: (I,R,W) S/U: (R,W) Domain0 Region04 : 0x0000000002000000-0x000000000200ffff M: (I,R,W) S/U: () Domain0 Region05 : 0x000000000c400000-0x000000000c5fffff M: (I,R,W) S/U: (R,W) Domain0 Region06 : 0x000000000c000000-0x000000000c3fffff M: (I,R,W) S/U: (R,W) Domain0 Region07 : 0x0000000000000000-0xffffffffffffffff M: () S/U: (R,W,X) Domain0 Next Address : 0x0000000080200000 Domain0 Next Arg1 : 0x0000000082200000 Domain0 Next Mode : S-mode Domain0 SysReset : yes Domain0 SysSuspend : yes Boot HART ID : 1 Boot HART Domain : root Boot HART Priv Version : v1.12 Boot HART Base ISA : rv64imafdcbvh Boot HART ISA Extensions : smstateen,sscofpmf,sstc,zicntr,zihpm,zicboz,zicbom,svpbmt,sdtrig,svade,smnpm,ssstateen,v,f,d Boot HART PMP Count : 16 Boot HART PMP Granularity : 2 bits Boot HART PMP Address Bits : 54 Boot HART MHPM Info : 16 (0x0007fff8) Boot HART Debug Triggers : 2 triggers Boot HART MIDELEG : 0x0000000000003666 Boot HART MEDELEG : 0x0000000000f4b509 WARNING: core-image-ptest-tar-1.0-r0 do_testimage: Last 25 lines of all logging (2983): Domain0 Region01 : 0x0000000080000000-0x000000008003ffff M: (F,R,X) S/U: () Domain0 Region02 : 0x0000000000100000-0x0000000000100fff M: (I,R,W) S/U: (R,W) Domain0 Region03 : 0x0000000010000000-0x0000000010000fff M: (I,R,W) S/U: (R,W) Domain0 Region04 : 0x0000000002000000-0x000000000200ffff M: (I,R,W) S/U: () Domain0 Region05 : 0x000000000c400000-0x000000000c5fffff M: (I,R,W) S/U: (R,W) Domain0 Region06 : 0x000000000c000000-0x000000000c3fffff M: (I,R,W) S/U: (R,W) Domain0 Region07 : 0x0000000000000000-0xffffffffffffffff M: () S/U: (R,W,X) Domain0 Next Address : 0x0000000080200000 Domain0 Next Arg1 : 0x0000000082200000 Domain0 Next Mode : S-mode Domain0 SysReset : yes Domain0 SysSuspend : yes Boot HART ID : 1 Boot HART Domain : root Boot HART Priv Version : v1.12 Boot HART Base ISA : rv64imafdcbvh Boot HART ISA Extensions : smstateen,sscofpmf,sstc,zicntr,zihpm,zicboz,zicbom,svpbmt,sdtrig,svade,smnpm,ssstateen,v,f,d Boot HART PMP Count : 16 Boot HART PMP Granularity : 2 bits Boot HART PMP Address Bits : 54 Boot HART MHPM Info : 16 (0x0007fff8) Boot HART Debug Triggers : 2 triggers Boot HART MIDELEG : 0x0000000000003666 Boot HART MEDELEG : 0x0000000000f4b509
qemuriscv64-ptest alma8-vk-1 master&master-next completed at 2026-08-23 00:57:16+00:00 https://valkyrie.yocto.io/pub/non-release/20260822-117/testresults/qemuriscv64-ptest/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2231/steps/16/logs/stdio
See if it happens again.
This issue is reproducible when building an image with KERNEL_DEBUG = "True" on riscv64. runqemu hangs when booting with -bios fw_jump.elf, but boots successfully with fw_dynamic.elf or the default bios. Hope this helps, Trevor.
Note that this requires meta-oe to make pahole-native available, otherwise you get: tgamblin@megalith ~/workspace/ypbuilds/poky-qemuriscv64/build $ bitbake core-image-minimal Loading cache: 100% |#################################################################################################################################################################################| Time: 0:00:00 Loaded 1979 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'pahole-native'. Close matches: pango-native patch-native patchelf-native ERROR: Required build target 'core-image-minimal' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal', 'virtual/kernel', 'pahole-native']
I can't reproduce this anymore. Harish, can you?
We've now switched to kernel version 7.2 with the Poky distro by default (see commit: https://git.yoctoproject.org/meta-yocto/commit/?id=3bb1295755628c4facec3a0a2800a9c12345ce00). This issue doesn't occur with the 7.2 kernel, so it looks like it may have been fixed in this version. To reproduce it, set PREFERRED_VERSION_linux-yocto = "6.18%" in local.conf. Note: wrynose is still affected.
I have sent a workaround patch to use fw_dynamic.elf for oe-core/wrynose branch. https://lists.openembedded.org/g/openembedded-core/message/245965
We should probably look at the kernel history to see what might've changed it before just going with a workaround. I'll spend some time doing that.
It seems that when I compare local builds between 6.18 and 7.2, the kernel build for the latter is reporting CONFIG_PAHOLE_VERSION=0 in the .config file. Still digging...