| Summary: | AB-INT: qemuriscv64-tc: rust.RustSelfTestSystemEmulated.test_rust failure: kernel segfault | ||
|---|---|---|---|
| Product: | [QA/Testing] Functional (self) Testing | Reporter: | Mathieu Dubois-Briand <mathieu.dubois-briand> |
| Component: | oe-selftest | Assignee: | Harish Sadineni <Harish.Sadineni> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | kexin.hao, paul, randy.macleod, sundeep.kokkonda, tgamblin |
| Version: | unspecified | ||
| Target Milestone: | 6.1 M3 | ||
| Hardware: | RISCV | ||
| OS: | Multiple | ||
| Whiteboard: | AB-INT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Mathieu Dubois-Briand
2025-09-01 08:02:15 UTC
qemuriscv64-tc fedora40-vk-4 master completed at 2025-08-29 02:06:48+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/58/builds/380/steps/12/logs/stdio I had this one sitting in my failure stack for a few days and I'm not really sure what to do with it. It is arm64, but it might still be related to this one. Or not... qemuarm64-tc debian12-vk-5 master completed at 2025-11-21 03:24:09+00:00 https://valkyrie.yocto.io/pub/non-release/20251121-9/testresults/qemuarm64-tc/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/2682/steps/13/logs/stdio Accidentally given to Trevor, move to TC team. Sundeep: from YP "Bug Stomping meeting", please prioritize this defect. The kernel has changed quite a bit so maybe it won't reproduce but we need data on that. With Latest kernel version 6.18.19 also the issue is being reproduced. Hi Harish, Do you have any further information on how this was reproduced? What command was run, was this on the autobuilder or on your own build environment, what was the host system and what was the command output? We observed the below segfault in riscv64 when testing on our local server (cmd: oe-selftest -r rust.RustSelfTestSystemEmulated.test_rust -K) The issue we see here is same as reprorted in this bug but at a different stage of build. The bug reprorted segfault is with a testcase failure but in our case the segfault hapenning during the stage2 build. Host information: Ubuntu 22.04.5 LTS (Jammy) Architecture: x86_64 ========= Error Text Begin ========= The following output was captured from the serial thread (formatted correctly): [ 702.343315] a[877]: unhandled signal 11 code 0x1 at 0x0000000000000000 in a[1ea8,2ae8ee4000+3000] [ 702.350031] CPU: 2 UID: 0 PID: 877 Comm: a Not tainted 6.18.28-yocto-standard #1 PREEMPT [ 702.351181] Hardware name: riscv-virtio,qemu (DT) [ 702.352035] epc : 0000002ae8ee5ea8 ra : 0000002ae8ee5ea6 sp : 0000003fd77e2230 [ 702.358295] gp : 0000002ae8ee8800 tp : 0000003f9e14a760 t0 : ffffffffffffffbf [ 702.359505] t1 : 0000002ae8ee540c t2 : 00000000000000f4 s0 : 0000002ae8ee9d80 [ 702.360536] s1 : 0000000000000002 a0 : 0000000000000000 a1 : 0000000000000001 [ 702.366502] a2 : 0000002ae8ee9db8 a3 : 0000000000000074 a4 : 0000000000000000 [ 702.367863] a5 : 0000000000000000 a6 : 0000000000000041 a7 : 0000003f9e413ce0 [ 702.368871] s2 : 0000002ae8ee9dd0 s3 : 0000002ae8ee9dd0 s4 : aaaaaaaaaaaaaaab [ 702.373389] s5 : 0000000000000018 s6 : 8000000000000000 s7 : 0000000000000008 [ 702.374731] s8 : 0000003f9e3e8aa8 s9 : 0000000000000000 s10: 0000000000000000 [ 702.376243] s11: 0000003fd77e2456 t3 : 0000003f9e1c9bec t4 : 0000000000000002 [ 702.382148] t5 : 0000000000000003 t6 : 00000000000000e0 [ 702.383164] status: 0000000200004020 badaddr: 0000000000000000 cause: 000000000000000f [ 702.384520] Code: f097 ffff 80e7 56c0 ed01 0097 0000 80e7 70c0 4585 (0023) 00b5 [ 742.545095] a[10583]: unhandled signal 4 code 0x1 at 0x0000002abe97a976 in a[1976,2abe979000+3000] [ 742.551965] CPU: 1 UID: 0 PID: 10583 Comm: a Not tainted 6.18.28-yocto-standard #1 PREEMPT [ 742.552655] Hardware name: riscv-virtio,qemu (DT) [ 742.553501] epc : 0000002abe97a976 ra : 0000002abe97a974 sp : 0000003ffe78f830 [ 742.554485] gp : 0000002abe97d800 tp : 0000003fb924b760 t0 : ffffffffffffffbf [ 742.555344] t1 : 0000002abe97a08c t2 : 00000000000000f4 s0 : 0000002abe97ed80 [ 742.556198] s1 : 0000000000000002 a0 : 0000000000000000 a1 : 000000000000006c [ 742.556987] a2 : 0000002abe97edb6 a3 : 000000000000006c a4 : 0000000000000000 [ 742.558061] a5 : 0000000000000000 a6 : 0000000000000041 a7 : 0000003fb9514ce0 [ 742.558862] s2 : 0000002abe97edd0 s3 : 0000002abe97edd0 s4 : aaaaaaaaaaaaaaab [ 742.559657] s5 : 0000000000000018 s6 : 8000000000000000 s7 : 0000000000000006 [ 742.560396] s8 : 0000003fb94e9aa8 s9 : 0000000000000000 s10: 0000000000000000 [ 742.561287] s11: 0000003ffe78f9d6 t3 : 0000003fb92cabec t4 : 0000000000000002 [ 742.562102] t5 : 0000000000000003 t6 : 00000000000000e0 [ 742.562696] status: 0000000200004020 badaddr: 0000000000000000 cause: 0000000000000002 [ 742.563610] Code: 0597 0000 8593 5555 4619 f097 ffff 80e7 7140 e511 (0000) 8e63 ========= Error Text End ========= The segfault failure from error message is due to: undefined reference to `__isoc23_strtoul' Additional observations: We observed the segfaluts are happening when there is a test case failure in riscv64 - Ref: https://autobuilder.yoctoproject.org/valkyrie/?#/builders/58/builds/1608/steps/13/logs/stdio In case of qemuarm64 with same test case failure there is no segfault: Ref: https://autobuilder.yoctoproject.org/valkyrie/?#/builders/5/builds/3783/steps/13/logs/stdio Based on these results, it looks like the segfault may be a RISC-V specific issue? qemuriscv64-tc debian13-vk-2 master completed at 2026-07-23 01:56:21+00:00 https://valkyrie.yocto.io/pub/non-release/20260723-8/testresults/qemuriscv64-tc/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/58/builds/1921/steps/13/logs/stdio |