From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: peter.maydell@linaro.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+
Date: Mon, 12 Aug 2013 15:02:11 -0400 [thread overview]
Message-ID: <52093133.9050306@windriver.com> (raw)
In-Reply-To: <52082EF8.10005@roeck-us.net>
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
>
next prev parent reply other threads:[~2013-08-12 20:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5207B3C3.9080508@roeck-us.net>
[not found] ` <20130811220450.GY23006@n2100.arm.linux.org.uk>
2013-08-12 0:40 ` [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+ Guenter Roeck
2013-08-12 16:24 ` Peter Maydell
2013-08-12 16:45 ` Russell King - ARM Linux
2013-08-12 17:33 ` Peter Maydell
2013-08-12 20:06 ` Russell King - ARM Linux
2013-08-12 20:49 ` Peter Maydell
2013-08-12 21:21 ` Russell King - ARM Linux
2013-08-12 21:36 ` Peter Maydell
2013-08-12 22:12 ` Russell King - ARM Linux
2013-08-12 22:48 ` Guenter Roeck
2013-08-12 23:04 ` Guenter Roeck
2013-08-14 10:33 ` Russell King - ARM Linux
2013-08-14 12:44 ` Peter Maydell
2013-08-14 12:49 ` Russell King - ARM Linux
2013-08-14 12:56 ` Peter Maydell
2013-08-14 14:41 ` Guenter Roeck
2013-08-14 15:26 ` [Qemu-devel] memory reads and writes Herbei Dacian
2013-08-12 17:48 ` [Qemu-devel] SCSI bus failures with qemu-arm in kernel 3.8+ Peter Maydell
2013-08-13 8:37 ` Rob Landley
2013-08-13 9:12 ` Peter Maydell
2013-08-13 11:30 ` Russell King - ARM Linux
2013-08-13 3:40 ` Guenter Roeck
2013-08-15 16:45 ` Peter Maydell
2013-08-15 17:54 ` Guenter Roeck
2013-08-15 18:05 ` Peter Maydell
2013-08-15 18:39 ` Guenter Roeck
2013-08-15 20:50 ` Guenter Roeck
2013-08-15 21:49 ` Peter Maydell
2013-08-15 22:18 ` Guenter Roeck
2013-08-15 22:23 ` Peter Maydell
2013-08-15 23:25 ` Guenter Roeck
2013-08-19 15:26 ` Guenter Roeck
2013-08-12 19:02 ` Paul Gortmaker [this message]
2013-08-12 20:58 ` Peter Maydell
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=52093133.9050306@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@roeck-us.net \
--cc=peter.maydell@linaro.org \
--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).