qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PULL 13/25] hcd-ohci: Fix inconsistency when resetting ohci root hu


From: BALATON Zoltan
Subject: Re: [PULL 13/25] hcd-ohci: Fix inconsistency when resetting ohci root hubs
Date: Wed, 15 Feb 2023 18:05:58 +0100 (CET)

On Wed, 15 Feb 2023, Laurent Vivier wrote:
On 2/15/23 15:34, Stefan Hajnoczi wrote:
On Wed, 15 Feb 2023 at 08:45, Qiang Liu <cyruscyliu@gmail.com> wrote:

Hi,

This commit breaks boot-serial-test on ppc64-softmmu.

   $ ./configure --enable-tcg-interpreter
'--target-list=aarch64-softmmu alpha-softmmu arm-softmmu hppa-softmmu
m68k-softmmu microblaze-softmmu ppc64-softmmu s390x-softmmu
x86_64-softmmu'
   $ make && cd build && QTEST_QEMU_BINARY=./qemu-system-ppc64
./tests/qtest/boot-serial-test; cd -

(Yes, the full --target-list is needed because boot-serial-test isn't
built when only ppc64-softmmu is selected.)

Here is the CI failure:
https://gitlab.com/qemu-project/qemu/-/jobs/3087540972#L22

I reproduced this failure and got "Out of malloc memory" error message in the [openbios-ppc](https://github.com/openbios/openbios/blob/4a0041107b8ef77e0e8337bfcb5f8078887261a7/libopenbios/ofmem_common.c#L134). However, I'm not sure how to debug this. Have you run into this issue before?

I don't. Maybe Gerd has an idea?

The memory allocation may be because there is either a request leak or
additional USB activity as a result of this patch.

It looks like a bug in openbios ohci, perhaps Zoltan can help?

Unfortunately I don't quite understand neither what this thread is about nor that openbios driver. Even though I've added that to openbios, all I did was porting the driver from coreboot's libpayload as noted in the copyright message of that file. So if you suspect it's a bug there you could try checking newer versions in libpayload and see if they've fixed anything that could help. On the other hand the OHCI emulation in QEMU is known to be incomplete and likely to have some bugs with guests that work on real hardware (e.g. MacOS <= 10.1) so it's more likely that QEMU behaves differently than it should assuming that the coreboot driver works on real hardware but I'm not sure about that either.

Regards,
BALATON Zoltan



reply via email to

[Prev in Thread] Current Thread [Next in Thread]