qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] lsi_scsi assertion


From: Jan Kiszka
Subject: Re: [Qemu-devel] lsi_scsi assertion
Date: Fri, 17 Sep 2010 14:55:39 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

Am 17.09.2010 14:51, Peter Lieven wrote:
> 
> Am 17.09.2010 um 14:38 schrieb Jan Kiszka:
> 
>> Am 17.09.2010 14:31, Peter Lieven wrote:
>>>
>>> Am 17.09.2010 um 14:30 schrieb Jan Kiszka:
>>>
>>>> Am 17.09.2010 14:26, Peter Lieven wrote:
>>>>>
>>>>> Am 17.09.2010 um 13:36 schrieb Bernhard Kohl:
>>>>>
>>>>>> Am 16.09.2010 15:57, schrieb ext Peter Lieven:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I found the following assertion in my log files after a system reset 
>>>>>>> was executed
>>>>>>>
>>>>>>> kvm: lsi_scsi: error: ORDERED queue not implemented
>>>>>>> last message repeated 5 times
>>>>>>> kvm: lsi_scsi: error: Unimplemented message 0x0d
>>>>>>> kvm: lsi_scsi: error: Unimplemented message 0x0c
>>>>>>> kvm: lsi_scsi: error: Unimplemented message 0x0d
>>>>>>> kvm: qemu-kvm-0.12.4.1: /usr/src/qemu-kvm-0.12.4/hw/lsi53c895a.c:596: 
>>>>>>> lsi_reselect: Assertion `s->current == ((void *)0)' failed.
>>>>>>> kvm: Aborted
>>>>>>> kvm errno=134
>>>>>>>
>>>>>>> The guest is a 64-bit ubuntu 10.04 server. Qemu-KVM is 0.12.4.
>>>>>>>
>>>>>>> Sounds this familiar to anyone?
>>>>>>>
>>>>>>> BR,
>>>>>>> Peter
>>>>>>
>>>>>> For messages 0x0c and 0x0d I recently submitted a patch:
>>>>>> http://thread.gmane.org/gmane.comp.emulators.qemu/79660
>>>>>
>>>>> thanks.
>>>>>
>>>>>>
>>>>>> ORDERED queue is still missing.
>>>>>> The assertion needs to be investigated. What guest OS?
>>>>>
>>>>> ubuntu 10.04.1 lts 64-bit
>>>>>
>>>>
>>>> Already checked if even the abort persists with 0.13-rc1? Just to
>>>> exclude that this is only a missing back-port.
>>>
>>> hi, not yet. i have not tried 0.13-rc1 because i did not find a valid 
>>> changelog in the distro.
>>
>> You mean you did not find any potentially related commit in git? There
>> were definitely changes regarding reset, and I don't think we have them
>> in 0.12 yet (backport was non-trivial, /me would have to check our local
>> patches for 0.12 if those turns out to be the key for your abort).
> 
> sorry, my sentence was not clear.
> 
> i downloaded 0.13-rc1 tarball from sourceforge and there are no entries 
> regarding
> 0.13-rc1 in the changelog.

That's the problem with meta-changelogs: someone has to update them
manually. The history is always in git (accessible via web as well).

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux



reply via email to

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