qemu-block
[Top][All Lists]
Advanced

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

Re: qemu-system-m68k: ../hw/scsi/scsi-disk.c:557: scsi_write_data: Asser


From: Mark Cave-Ayland
Subject: Re: qemu-system-m68k: ../hw/scsi/scsi-disk.c:557: scsi_write_data: Assertion `r->req.aiocb == NULL' failed.
Date: Wed, 16 Aug 2023 14:35:24 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0

On 16/08/2023 12:30, Waldemar Brodkorb wrote:

Hi,
Philippe Mathieu-Daudé wrote,

Hi Waldemar

On 13/8/23 09:46, Waldemar Brodkorb wrote:
Hi,

I am using Qemu 8.0.3 and getting this error:
qemu-system-m68k: ../hw/scsi/scsi-disk.c:557: scsi_write_data: Assertion 
`r->req.aiocb == NULL' failed.

It happens f.e. when I extract the glibc source code inside Linux.
Linux 6.1.44, glibc 2.38 is used for the Linux system.
I am starting qemu this way:
qemu-system-m68k -nographic -M q800 -kernel 
/home/wbx/openadk/firmware/qemu-m68k-q800_glibc_68040/qemu-m68k-q800-archive-kernel
 qemu-m68k.img

What can I do about it? Why this is happening on "heavy" I/O usage?

Cc'ing the qemu-block list.

Do you mind filling a bug report at
https://gitlab.com/qemu-project/qemu/-/issues ?

Okay, see here:
https://gitlab.com/qemu-project/qemu/-/issues/1831

Thanks for the bug report! I'm currently working on improving the ESP emulation, so I can add your test case to my current suite of test images. My guess is that the write interrupt isn't being delayed correctly and so the assert() triggers due to buffer underflow.

Please can you upload the binary images to the bug report to allow me to try and reproduce this issue? The ESP code tends to be timing sensitive across kernel versions and OSs, so without this it will be difficult to reproduce.


ATB,

Mark.




reply via email to

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