All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: -device T,help crashes
Date: Thu, 12 Mar 2026 09:15:17 +0100	[thread overview]
Message-ID: <87bjgtzcoa.fsf@pond.sub.org> (raw)
In-Reply-To: <87pl5abgpl.fsf@pond.sub.org> (Markus Armbruster's message of "Wed, 11 Mar 2026 15:09:42 +0100")

Markus Armbruster <armbru@redhat.com> writes:

> Watch this:
>
>     $ qemu-system-aarch64 -S -display none -M virt -device acpi-ged,help
>     qemu-system-aarch64: ../hw/core/qdev.c:858: qdev_get_machine: Assertion `dev' failed.
>
> A number of devices crash this way:
>
> * acpi-ged (aarch64 arm i386 loongarch64 x86_64)
> * fsl-imx6 (aarch64 arm)
> * fsl-imx7 (aarch64 arm)
> * fsl-imx8mp (aarch64)
> * microchip.pfsoc (riscv64)
> * riscv.sifive.e.soc (riscv32 riscv64)
> * xlnx-zynqmp (aarch64)

Alistair Francis posted a fix

    Subject: [PATCH 0/7] Fix some -device T,help crashes
    Date: Thu, 12 Mar 2026 14:31:51 +1000
    Message-ID: <20260312043158.4191378-1-alistair.francis@wdc.com>

Thanks, Alistair!

> Here's another one:
>
>     $ qemu-system-sparc64 -S -display none -M virt -device sun4u-iommu,help
>     qemu-system-sparc64: ../system/physmem.c:1401: register_multipage: Assertion `num_pages' failed.
>
> Devices crashing this way:
>
> * Loongson-3A4000-mips64-cpu (mips64 mips64el)
> * dc232b-xtensa-cpu (xtensa)
> * dc233c-xtensa-cpu (xtensa)
> * de212-xtensa-cpu (xtensa)
> * de233_fpu-xtensa-cpu (xtensa)
> * dsp3400-xtensa-cpu (xtensa)
> * fsf-xtensa-cpu (xtensaeb)
> * lx106-xtensa-cpu (xtensa)
> * sample_controller-xtensa-cpu (xtensa)
> * sun4m-iommu (sparc)
> * sun4u-iommu (sparc64)
> * test_kc705_be-xtensa-cpu (xtensaeb)
> * test_mmuhifi_c3-xtensa-cpu (xtensa)

Thomas Huth posted fixes for mips and xtensa

    Subject: [PATCH] target/mips/cpu: Move initialization of memory region to realize function 
    Date: Wed, 11 Mar 2026 22:16:29 +0100
    Message-ID: <20260311211629.118608-1-thuth@redhat.com>

    Subject: [PATCH] target/xtensa/cpu: Move initialization of memory region to realize function
    Date: Wed, 11 Mar 2026 21:25:03 +0100
    Message-ID: <20260311202503.107026-1-thuth@redhat.com>

Thanks, Thomas!

We still need a fix for sparc.

> These crashes escape tests/qtest/device-introspect-test, because it
> covers only HMP "device_add T,help", not CLI "-device T,help".

Anyone wants to cook up a patch to cover -device?



  parent reply	other threads:[~2026-03-12  8:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 14:09 -device T,help crashes Markus Armbruster
2026-03-11 14:55 ` Peter Maydell
2026-03-11 15:14   ` Thomas Huth
2026-03-12  8:05     ` Markus Armbruster
2026-03-11 15:16 ` BALATON Zoltan
2026-03-12  8:15 ` Markus Armbruster [this message]
2026-03-17  6:24   ` Thomas Huth
2026-03-17  7:35     ` Markus Armbruster
2026-03-17  8:12       ` Thomas Huth
2026-03-17  9:27         ` Markus Armbruster
2026-03-17  9:37           ` Thomas Huth
2026-03-17 10:30             ` Markus Armbruster

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=87bjgtzcoa.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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.