Bug 16431 - AB-INT RISCV64: core-image-ptest-python3-click central error
Summary: AB-INT RISCV64: core-image-ptest-python3-click central error
Status: ACCEPTED
Alias: None
Product: Package Testing (ptest)
Classification: QA/Testing
Component: ptest (show other bugs)
Version: unspecified
Hardware: RISCV Multiple
: Medium+ normal
Target Milestone: 6.2 M1
Assignee: Trevor Gamblin
QA Contact:
URL:
Whiteboard: AB-INT
Depends on:
Blocks:
 
Reported: 2026-09-18 08:11 UTC by João Marcos Costa
Modified: 2026-09-28 18:38 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description João Marcos Costa 2026-09-18 08:11:49 UTC
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2399/steps/16/logs/stdio

"""
AssertionError: 3 != 0 : Log: /srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/build/tmp/work/qemuriscv64-poky-linux/core-image-ptest-python3-click/1.0/target_logs/dmesg_output.log
-----------------------
Central error: [   12.303938] ------------[ cut here ]------------
***********************
[    1.425802]     HOME=/
[    1.425820]     TERM=linux
[    1.478659] input: QEMU QEMU USB Tablet as /devices/platform/soc/30000000.pci/pci0000:00/0000:00:02.0/usb1/1-1/1-1:1.0/0003:0627:0001.0001/input/input0
[    1.482083] hid-generic 0003:0627:0001.0001: input: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:02.0-1/input0
[    1.603879] usb 1-2: new high-speed USB device number 3 using xhci_hcd
[    1.750844] input: QEMU QEMU USB Keyboard as /devices/platform/soc/30000000.pci/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.0/0003:0627:0001.0002/input/input1
[    1.812699] hid-generic 0003:0627:0001.0002: input: USB HID v1.11 Keyboard [QEMU QEMU USB Keyboard] on usb-0000:00:02.0-2/input0
[    1.882350] udevd[126]: starting version 3.2.14
[    1.927748] udevd[127]: starting eudev-3.2.14
[    2.228151] EXT4-fs (vda): re-mounted 27f562ed-e113-41d5-9ec7-cd8a20b4b83d.
[   12.303938] ------------[ cut here ]------------
"""

qemuriscv64-ptest rocky8-vk-1
Comment 1 João Marcos Costa 2026-09-18 08:14:34 UTC
The same kind of error happening here, but for other packages:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2403/steps/16/logs/stdio

qemuriscv64-ptest alma8-vk-1

Example:

AssertionError: 4 != 0 : Log: /srv/pokybuild/yocto-worker/qemuriscv64-ptest/build/build/tmp/work/qemuriscv64-poky-linux/core-image-ptest-sed/1.0/target_logs/dmesg_output.log
-----------------------
Central error: [    5.984437] ------------[ cut here ]------------
***********************
[    2.939541] hid-generic 0003:0627:0001.0002: input: USB HID v1.11 Keyboard [QEMU QEMU USB Keyboard] on usb-0000:00:02.0-2/input0
[    3.016571] Freeing unused kernel image (initmem) memory: 2708K
[    3.018335] Run /sbin/init as init process
[    3.020052]   with arguments:
[    3.020085]     /sbin/init
[    3.020115]   with environment:
[    3.020138]     HOME=/
[    3.020168]     TERM=linux
[    4.811432] udevd[123]: starting version 3.2.14
[    4.886231] udevd[124]: starting eudev-3.2.14
[    5.984437] ------------[ cut here ]------------
[    6.099936] bochs-drm 0000:00:03.0: [drm] vblank wait timed out on crtc 0
[    6.101481] WARNING: /usr/src/kernel/drivers/gpu/drm/drm_vblank.c:1329 at drm_crtc_wait_one_vblank+0x174/0x1f0, CPU#2: kworker/2:1/47
[    6.101927] Modules linked in:
[    6.102287] CPU: 2 UID: 0 PID: 47 Comm: kworker/2:1 Not tainted 7.2.4-yocto-standard #1 PREEMPT 
[    6.102400] Hardware name: riscv-virtio,qemu (DT)
[    6.102574] Workqueue: events drm_fb_helper_damage_work
[    6.102736] epc : drm_crtc_wait_one_vblank+0x174/0x1f0
[    6.102813]  ra : drm_crtc_wait_one_vblank+0x174/0x1f0
[    6.102853] epc : ffffffff808d9b2c ra : ffffffff808d9b2c sp : ffffffc6001abbd0
[    6.102876]  gp : ffffffff81a1ded8 tp : ffffffd602784380 t0 : ffffffff800223c0

***********************
Central error: [    7.819416] ------------[ cut here ]------------
Comment 2 Trevor Gamblin 2026-09-28 18:37:33 UTC
Not the first time I've looked into this issue, but note that
Comment 3 Trevor Gamblin 2026-09-28 18:38:42 UTC
Not the first time I've looked into such an issue. Note that qemuriscv chooses a different QB_GRAPHICS default option than other architectures:

tgamblin@megalith ~/workspace/ypbuilds/poky-qemuriscv64/layers/openembedded-core (master)$ grep -r "QB_GRAPHICS"
meta/classes-recipe/qemuboot.bbclass:# QB_GRAPHICS: QEMU video card type (e.g. "-vga std")
meta/classes-recipe/qemuboot.bbclass:QB_GRAPHICS ?= ""
meta/conf/machine/include/mips/qemuboot-mips.inc:QB_GRAPHICS = "-vga std"
grep: meta/conf/machine/include/riscv/.qemuriscv.inc.swp: binary file matches
meta/conf/machine/include/riscv/qemuriscv.inc:QB_GRAPHICS = "-device bochs-display"
meta/conf/machine/qemuarm.conf:QB_GRAPHICS = "-device virtio-gpu-pci"
meta/conf/machine/qemuarm64.conf:QB_GRAPHICS = "-device virtio-gpu-pci"
meta/conf/machine/qemuarmv5.conf:QB_GRAPHICS = "-device virtio-gpu-pci"
scripts/runqemu:        self.qemu_opt += ' %s' %self.get('QB_GRAPHICS')

Looking into this a bit...