qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Waldemar Brodkorb <wbx@openadk.org>, qemu-devel@nongnu.org
Cc: qemu-block <qemu-block@nongnu.org>
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 11:15:59 +0200	[thread overview]
Message-ID: <389cfe6d-aade-f79a-b618-fb0e029fff5d@linaro.org> (raw)
In-Reply-To: <ZNiKYwbkk5zwlLB5@waldemar-brodkorb.de>

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 ?

Regards,

Phil.

> 
> Thanks for any help
>   Waldemar
> 
> 



  parent reply	other threads:[~2023-08-16  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-13  7:46 qemu-system-m68k: ../hw/scsi/scsi-disk.c:557: scsi_write_data: Assertion `r->req.aiocb == NULL' failed Waldemar Brodkorb
2023-08-14 10:56 ` Thomas Huth
2023-08-15 10:26   ` Waldemar Brodkorb
2023-08-16  9:15 ` Philippe Mathieu-Daudé [this message]
2023-08-16 11:30   ` Waldemar Brodkorb
2023-08-16 13:35     ` Mark Cave-Ayland

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=389cfe6d-aade-f79a-b618-fb0e029fff5d@linaro.org \
    --to=philmd@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wbx@openadk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).