From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Lieven <pl@dlh.net>
Cc: ext Kevin Wolf <kwolf@redhat.com>,
Bernhard Kohl <bernhard.kohl@nsn.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] lsi_scsi assertion
Date: Fri, 17 Sep 2010 14:38:27 +0200 [thread overview]
Message-ID: <4C936143.2010401@siemens.com> (raw)
In-Reply-To: <4D991DB7-E6CA-47B2-A516-FA816610C1F7@dlh.net>
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).
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-09-17 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 13:57 [Qemu-devel] lsi_scsi assertion Peter Lieven
2010-09-17 11:36 ` Bernhard Kohl
2010-09-17 12:26 ` Peter Lieven
2010-09-17 12:30 ` Jan Kiszka
2010-09-17 12:31 ` Peter Lieven
2010-09-17 12:38 ` Jan Kiszka [this message]
2010-09-17 12:51 ` Peter Lieven
2010-09-17 12:55 ` Jan Kiszka
2010-09-17 13:16 ` Bernhard Kohl
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=4C936143.2010401@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=bernhard.kohl@nsn.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=pl@dlh.net \
--cc=qemu-devel@nongnu.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).