[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] lsi53c895a lsi_do_dma assertion failure
From: |
Markus Armbruster |
Subject: |
Re: [Qemu-devel] lsi53c895a lsi_do_dma assertion failure |
Date: |
Tue, 17 Mar 2015 08:22:38 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
Paolo Bonzini <address@hidden> writes:
> On 16/03/2015 16:59, Chris Takemura wrote:
>> Hi everyone,
>>
>> We're using qemu as a device model for xen 4.4. Lately we've been
>> having qemu crashes with this output:
>>
>> lsi_scsi: error: Unhandled writeb 0xff = 0x0
>>
>> lsi_scsi: error: Unhandled writeb 0x100 = 0x0
>>
>> lsi_scsi: error: Unhandled writeb 0x101 = 0x0
>>
>> lsi_scsi: error: Unhandled writeb 0x102 = 0x0
>>
>> qemu-system-i386: /home/chris/qemu/hw/scsi/lsi53c895a.c:541: lsi_do_dma:
>> Assertion `s->current' failed.
>>
>>
>> This is with a clean qemu-2.1.0 tree, built for Xen.
>>
>> I confirmed that commit d1d74664ea99cdc571afee12e31c8625595765b0 is
>> present in our code. (As described in the thread that begins
>> with
>> http://qemu-devel.nongnu.narkive.com/LtGj28sZ/win2k8-32-bit-mix-of-ide-and-scsi-assertion
>> ).
>
> What guest is this? The answer is basically "do not use this device
> model", it is old and buggy and newer guests do not even ship the driver
> anymore.
I agree with the advice, but I can't help to notice we're not taking it
ourselves: -device if=scsi still creates lsi53c895a HBAs for many
machines. I think we should fix that for new machine models.