From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [Qemu-devel] lsi_scsi assertion Date: Fri, 17 Sep 2010 14:55:39 +0200 Message-ID: <4C93654B.3070700@siemens.com> References: <4C922233.6030602@dlh.net> <4C9352BA.3090808@nsn.com> <1494275E-AE25-47E7-B800-739B40C336F1@dlh.net> <4C935F81.7040103@siemens.com> <4D991DB7-E6CA-47B2-A516-FA816610C1F7@dlh.net> <4C936143.2010401@siemens.com> <2B7AD5B2-8EC7-4574-8C06-1E0D5864E64F@dlh.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Bernhard Kohl , ext Kevin Wolf , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" To: Peter Lieven Return-path: Received: from thoth.sbs.de ([192.35.17.2]:21454 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753793Ab0IQM4A (ORCPT ); Fri, 17 Sep 2010 08:56:00 -0400 In-Reply-To: <2B7AD5B2-8EC7-4574-8C06-1E0D5864E64F@dlh.net> Sender: kvm-owner@vger.kernel.org List-ID: 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=46080 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OwaWW-0007h1-WA for qemu-devel@nongnu.org; Fri, 17 Sep 2010 08:58:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OwaTg-0007Wz-RX for qemu-devel@nongnu.org; Fri, 17 Sep 2010 08:55:46 -0400 Received: from thoth.sbs.de ([192.35.17.2]:21390) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OwaTg-0007WN-Ex for qemu-devel@nongnu.org; Fri, 17 Sep 2010 08:55:44 -0400 Message-ID: <4C93654B.3070700@siemens.com> Date: Fri, 17 Sep 2010 14:55:39 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Qemu-devel] lsi_scsi assertion References: <4C922233.6030602@dlh.net> <4C9352BA.3090808@nsn.com> <1494275E-AE25-47E7-B800-739B40C336F1@dlh.net> <4C935F81.7040103@siemens.com> <4D991DB7-E6CA-47B2-A516-FA816610C1F7@dlh.net> <4C936143.2010401@siemens.com> <2B7AD5B2-8EC7-4574-8C06-1E0D5864E64F@dlh.net> In-Reply-To: <2B7AD5B2-8EC7-4574-8C06-1E0D5864E64F@dlh.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: ext Kevin Wolf , Bernhard Kohl , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" 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