Re: qemu-system-m68k: ../hw/scsi/scsi-disk.c:557: scsi_write_data: Assertion `r->req.aiocb == NULL' failed.

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.aioc

Re: qemu-system-m68k: ../hw/scsi/scsi-disk.c:557: scsi_write_data: Assertion `r->req.aiocb == NULL' failed.

Hi, Thomas Huth wrote, > On 13/08/2023 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. > >

qemu-system-m68k: ../hw/scsi/scsi-disk.c:557: scsi_write_data: Assertion `r->req.aiocb == NULL' failed.

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 t

problem with qemu-system-loongarch64

Hi Qemu developers, I am trying to bootup a loongarch64 Linux kernel in Qemu 7.1.0-rc2. The problem is I get no output when using following command: qemu-system-loongarch64 -M virt -nographic -kernel vmlinux You can find my vmlinux initramfs here: https://debug.openadk.org/vmlinux It is cross-co

Re: [Qemu-devel] Deprecate tilegx ?

Hi, > Am 09.03.2018 um 16:13 schrieb Alex Bennée : > > > Bastian Koppelmann writes: > >>> On 02/28/2018 07:11 AM, Thomas Huth wrote: On 27.02.2018 12:51, Peter Maydell wrote: I propose that we deprecate and plan to remove the unicore32 code: >>> [...] >> [...] >>> >>> Sounds reasona

Re: [Qemu-devel] [PATCH v2] qemu-m68k: add support for interrupt masking/unmasking

Hi Stefan, Stefan Weil wrote, > Am 03.04.2015 um 10:04 schrieb Waldemar Brodkorb: > >Hi Stefan, > >Stefan Weil wrote, > > > >>Am 29.03.2015 um 17:53 schrieb Stefan Weil: > >>>Am 29.03.2015 um 15:47 schrieb Waldemar Brodkorb: > >>>>Hi Ste

Re: [Qemu-devel] [PATCH v2] qemu-m68k: add support for interrupt masking/unmasking

Hi Stefan, Stefan Weil wrote, > Am 29.03.2015 um 17:53 schrieb Stefan Weil: > >Am 29.03.2015 um 15:47 schrieb Waldemar Brodkorb: > >>Hi Stefan, > >>Stefan Weil wrote, > >> > >>>You can debug the kernel panic by attaching a cross debugger to the >

Re: [Qemu-devel] [PATCH v2] qemu-m68k: add support for interrupt masking/unmasking

Hi Stefan, Stefan Weil wrote, > Am 28.03.2015 um 17:07 schrieb Waldemar Brodkorb: > >Fixes following problem, when trying to boot linux: > >qemu: hardware error: mcf_intc_write: Bad write offset 28 > > > >CPU #0: > >D0 = 00ff A0 = 402ea5dc F0 =

[Qemu-devel] [PATCH v2] qemu-m68k: add support for interrupt masking/unmasking

/pipermail/buildroot/2012-April/052585.html Signed-off-by: Thomas Petazzoni Tested-by: Waldemar Brodkorb Signed-off-by: Waldemar Brodkorb --- v1 -> v2: - add {} to conform to Qemu Coding Style suggested by Stefan Weil - add short comments to case statements with return 0 suggested

[Qemu-devel] [PATCH] qemu-m68k: add support for interrupt masking/unmasking

/pipermail/buildroot/2012-April/052585.html Signed-off-by: Thomas Petazzoni Tested-by: Waldemar Brodkorb Signed-off-by: Waldemar Brodkorb --- hw/m68k/mcf_intc.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/hw/m68k/mcf_intc.c b/hw/m68k/mcf_intc.c index 621423c..1d161b1

[Qemu-devel] qemu-arm does not boot kernel since 3.19

Hi, I am regulary using qemu with arm. Since Linux 3.19 my system no longer boots. I am using Qemu 2.2.0 on Linux/amd64. System is started via: qemu-system-arm -nographic -M vexpress-a9 -cpu cortex-a9 -net user -net nic,model=lan9118 -kernel qemu-arm-initramfspiggyback-kernel I have read, they c