From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754156Ab3HLUPg (ORCPT ); Mon, 12 Aug 2013 16:15:36 -0400 Received: from mail7.windriver.com ([128.224.252.3]:41108 "EHLO mail7.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751136Ab3HLUPc (ORCPT ); Mon, 12 Aug 2013 16:15:32 -0400 X-Greylist: delayed 4344 seconds by postgrey-1.27 at vger.kernel.org; Mon, 12 Aug 2013 16:15:32 EDT Message-ID: <52093133.9050306@windriver.com> Date: Mon, 12 Aug 2013 15:02:11 -0400 From: Paul Gortmaker User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: Guenter Roeck CC: Russell King - ARM Linux , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , , Subject: Re: SCSI bus failures with qemu-arm in kernel 3.8+ References: <5207B3C3.9080508@roeck-us.net> <20130811220450.GY23006@n2100.arm.linux.org.uk> <52082EF8.10005@roeck-us.net> In-Reply-To: <52082EF8.10005@roeck-us.net> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [128.224.146.65] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13-08-11 08:40 PM, Guenter Roeck wrote: > On 08/11/2013 03:04 PM, Russell King - ARM Linux wrote: >> On Sun, Aug 11, 2013 at 08:54:43AM -0700, Guenter Roeck wrote: >>> Hi, >>> >>> trying to boot arm versatile images with qemu results in the following error >>> if I try to boot with a disk image. >>> >>> sym0: <895a> rev 0x0 at pci 0000:00:0d.0 irq 92 >>> sym0: SCSI BUS has been reset. >>> scsi0 : sym-2.2.3 >>> [...] >>> scsi 0:0:0:0: ABORT operation started >>> scsi 0:0:0:0: ABORT operation timed-out. >>> [...] >>> >>> Yocto's 3.8 kernel images work, upstream kernels 3.8 and later fail >>> (I did not check if/how earlier kernels are affected). >>> >>> Tracking this down shows that the problem is known and has been fixed with >>> commit 351d1339 (arm: add dummy swizzle for versatile with qemu) in the >>> Yocto 3.8 kernel at git://git.yoctoproject.org/linux-yocto-3.8. >>> >>> Would it be possible to submit this patch for inclusion into affected upstream kernels ? >> >> It could be that it's qemu's PCI routing is wrong - it's not the first >> time that qemu has got something wrong. >> >> Unfortunately, the PCI routing is totally undocumented, and as I understand >> it, there's very few backplanes out there now that finding out their real >> routing is virtually impossible. I'm loathed to change it unless someone >> can point to a definitive source of information on this. >> > > Maybe Paul can comment, as he wrote the patch. If I recall correctly, I'd showed the patch to Russell at the time (via IRC, I believe) and he'd told me essentially the same thing as the above paragraph, which is why I didn't put it in the patch system, and why the commit log of the yocto patch (http://goo.gl/riEZXY) reads as it does (i.e. it is unclear what the real swizzle is). If docs appear that help clarify where the real issue is, then great. Paul. -- > > If it helps, I tried with qemu 1.4.0 from Ubuntu 13.4, qemu 1.4.0 from Poky 1.4.0-1, > and qemu 1.5.2 from the qemu repository. > > Copying qemu-devel to increase the audience. > > Guenter > From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48535) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V8yWg-0007kb-BN for qemu-devel@nongnu.org; Mon, 12 Aug 2013 16:15:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V8yWZ-0007GA-KD for qemu-devel@nongnu.org; Mon, 12 Aug 2013 16:15:38 -0400 Received: from mail7.windriver.com ([128.224.252.3]:41094) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V8yWZ-0007FR-2X for qemu-devel@nongnu.org; Mon, 12 Aug 2013 16:15:31 -0400 Message-ID: <52093133.9050306@windriver.com> Date: Mon, 12 Aug 2013 15:02:11 -0400 From: Paul Gortmaker MIME-Version: 1.0 References: <5207B3C3.9080508@roeck-us.net> <20130811220450.GY23006@n2100.arm.linux.org.uk> <52082EF8.10005@roeck-us.net> In-Reply-To: <52082EF8.10005@roeck-us.net> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+ List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Guenter Roeck Cc: peter.maydell@linaro.org, Russell King - ARM Linux , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , qemu-devel@nongnu.org On 13-08-11 08:40 PM, Guenter Roeck wrote: > On 08/11/2013 03:04 PM, Russell King - ARM Linux wrote: >> On Sun, Aug 11, 2013 at 08:54:43AM -0700, Guenter Roeck wrote: >>> Hi, >>> >>> trying to boot arm versatile images with qemu results in the following error >>> if I try to boot with a disk image. >>> >>> sym0: <895a> rev 0x0 at pci 0000:00:0d.0 irq 92 >>> sym0: SCSI BUS has been reset. >>> scsi0 : sym-2.2.3 >>> [...] >>> scsi 0:0:0:0: ABORT operation started >>> scsi 0:0:0:0: ABORT operation timed-out. >>> [...] >>> >>> Yocto's 3.8 kernel images work, upstream kernels 3.8 and later fail >>> (I did not check if/how earlier kernels are affected). >>> >>> Tracking this down shows that the problem is known and has been fixed with >>> commit 351d1339 (arm: add dummy swizzle for versatile with qemu) in the >>> Yocto 3.8 kernel at git://git.yoctoproject.org/linux-yocto-3.8. >>> >>> Would it be possible to submit this patch for inclusion into affected upstream kernels ? >> >> It could be that it's qemu's PCI routing is wrong - it's not the first >> time that qemu has got something wrong. >> >> Unfortunately, the PCI routing is totally undocumented, and as I understand >> it, there's very few backplanes out there now that finding out their real >> routing is virtually impossible. I'm loathed to change it unless someone >> can point to a definitive source of information on this. >> > > Maybe Paul can comment, as he wrote the patch. If I recall correctly, I'd showed the patch to Russell at the time (via IRC, I believe) and he'd told me essentially the same thing as the above paragraph, which is why I didn't put it in the patch system, and why the commit log of the yocto patch (http://goo.gl/riEZXY) reads as it does (i.e. it is unclear what the real swizzle is). If docs appear that help clarify where the real issue is, then great. Paul. -- > > If it helps, I tried with qemu 1.4.0 from Ubuntu 13.4, qemu 1.4.0 from Poky 1.4.0-1, > and qemu 1.5.2 from the qemu repository. > > Copying qemu-devel to increase the audience. > > Guenter > From mboxrd@z Thu Jan 1 00:00:00 1970 From: paul.gortmaker@windriver.com (Paul Gortmaker) Date: Mon, 12 Aug 2013 15:02:11 -0400 Subject: SCSI bus failures with qemu-arm in kernel 3.8+ In-Reply-To: <52082EF8.10005@roeck-us.net> References: <5207B3C3.9080508@roeck-us.net> <20130811220450.GY23006@n2100.arm.linux.org.uk> <52082EF8.10005@roeck-us.net> Message-ID: <52093133.9050306@windriver.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 13-08-11 08:40 PM, Guenter Roeck wrote: > On 08/11/2013 03:04 PM, Russell King - ARM Linux wrote: >> On Sun, Aug 11, 2013 at 08:54:43AM -0700, Guenter Roeck wrote: >>> Hi, >>> >>> trying to boot arm versatile images with qemu results in the following error >>> if I try to boot with a disk image. >>> >>> sym0: <895a> rev 0x0 at pci 0000:00:0d.0 irq 92 >>> sym0: SCSI BUS has been reset. >>> scsi0 : sym-2.2.3 >>> [...] >>> scsi 0:0:0:0: ABORT operation started >>> scsi 0:0:0:0: ABORT operation timed-out. >>> [...] >>> >>> Yocto's 3.8 kernel images work, upstream kernels 3.8 and later fail >>> (I did not check if/how earlier kernels are affected). >>> >>> Tracking this down shows that the problem is known and has been fixed with >>> commit 351d1339 (arm: add dummy swizzle for versatile with qemu) in the >>> Yocto 3.8 kernel at git://git.yoctoproject.org/linux-yocto-3.8. >>> >>> Would it be possible to submit this patch for inclusion into affected upstream kernels ? >> >> It could be that it's qemu's PCI routing is wrong - it's not the first >> time that qemu has got something wrong. >> >> Unfortunately, the PCI routing is totally undocumented, and as I understand >> it, there's very few backplanes out there now that finding out their real >> routing is virtually impossible. I'm loathed to change it unless someone >> can point to a definitive source of information on this. >> > > Maybe Paul can comment, as he wrote the patch. If I recall correctly, I'd showed the patch to Russell at the time (via IRC, I believe) and he'd told me essentially the same thing as the above paragraph, which is why I didn't put it in the patch system, and why the commit log of the yocto patch (http://goo.gl/riEZXY) reads as it does (i.e. it is unclear what the real swizzle is). If docs appear that help clarify where the real issue is, then great. Paul. -- > > If it helps, I tried with qemu 1.4.0 from Ubuntu 13.4, qemu 1.4.0 from Poky 1.4.0-1, > and qemu 1.5.2 from the qemu repository. > > Copying qemu-devel to increase the audience. > > Guenter >