From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Weiwei Li <liwei1518@gmail.com>,
Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
Chao Liu <chao.liu@processmission.com>,
qemu-riscv@nongnu.org
Subject: Introspecting max32-riscv-cpu after rva23s64-riscv-cpu crashes
Date: Wed, 21 Oct 2026 14:42:09 +0200 [thread overview]
Message-ID: <87ld7rmdi6.fsf@pond.sub.org> (raw)
Watch this:
$ qemu-system-riscv64 -S -nodefaults -display none -M none -qmp stdio
{"QMP": {"version": {"qemu": {"micro": 50, "minor": 1, "major": 11}, "package": "v11.1.0-2545-g2d150b99ce-dirty"}, "capabilities": ["oob"]}}
{"execute": "qmp_capabilities", "arguments": {"enable": ["oob"]}}
{"return": {}}
{"execute": "qom-list-properties", "arguments": {"typename": "rva23s64-riscv-cpu"}}
[Expected output...]
{"execute": "qom-list-properties", "arguments": {"typename": "max32-riscv-cpu"}}
**
ERROR:../target/riscv/cpu.c:516:satp_mode_str: code should not be reached
Bail out! ERROR:../target/riscv/cpu.c:516:satp_mode_str: code should not be reached
Aborted (core dumped) ../qemu/bld/qemu-system-riscv64 -S -nodefaults -display none -M none -qmp stdio
This is satp_mode_str(VM_1_10_SV39, false). Interesting part of stack
backtrace:
#4 0x00007f9d6e7cd447 in g_assertion_message_expr ()
at /lib64/libglib-2.0.so.0
#5 0x000055801fc2f556 in satp_mode_str
(satp_mode=<optimized out>, is_32_bit=<optimized out>)
at ../target/riscv/cpu.c:516
#6 0x000055801fca193c in riscv_cpu_set_profile
(cpu=0x55802e5b8c90, profile=profile@entry=0x5580209732e0 <RVA22S64>, enabled=enabled@entry=true) at ../target/riscv/tcg/tcg-cpu.c:1305
#7 0x000055801fca1cf7 in riscv_cpu_add_profiles (cpu_obj=<optimized out>)
at ../target/riscv/tcg/tcg-cpu.c:1549
#8 riscv_cpu_add_user_properties (obj=0x55802e5b8c90)
at ../target/riscv/tcg/tcg-cpu.c:1622
#9 riscv_tcg_cpu_instance_init (cs=<optimized out>)
at ../target/riscv/tcg/tcg-cpu.c:1741
#10 0x000055801fd178a7 in object_init_with_type
(obj=0x55802e5b8c90, ti=<optimized out>) at ../qom/object.c:430
#11 object_init_with_type (obj=0x55802e5b8c90, ti=<optimized out>)
at ../qom/object.c:426
#12 object_init_with_type (obj=0x55802e5b8c90, ti=0x55802e2e0250)
at ../qom/object.c:426
#13 object_initialize_with_type
(obj=0x55802e5b8c90, size=<optimized out>, type=0x55802e2e0250)
at ../qom/object.c:512
#14 0x000055801fd17c5f in object_new_with_type (type=0x55802e2e0250)
at ../qom/object.c:710
#15 0x000055801fe17276 in qmp_qom_list_properties
(typename=0x55802e5ab3d0 "max32-riscv-cpu", errp=0x22c5a0,
errp@entry=0x7ffe4a494aa0) at ../qom/qom-qmp-cmds.c:283
next reply other threads:[~2026-10-21 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 12:42 Markus Armbruster [this message]
2026-10-21 13:09 ` Introspecting max32-riscv-cpu after rva23s64-riscv-cpu crashes Philippe Mathieu-Daudé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ld7rmdi6.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=chao.liu@processmission.com \
--cc=daniel.barboza@oss.qualcomm.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.