From: "Marc Marí" <marc.mari.barcelo@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Linux 3.4, VersatilePB and PCI
Date: Tue, 13 Jan 2015 12:02:29 +0100 [thread overview]
Message-ID: <20150113120229.2883a1e2@crunchbang> (raw)
In-Reply-To: <CAFEAcA_7brSQ1UuXZaCYp2BtpKOi=LE752RLv49VYkKhpAx5YQ@mail.gmail.com>
El Tue, 13 Jan 2015 10:46:20 +0000
Peter Maydell <peter.maydell@linaro.org> escribió:
> On 13 January 2015 at 10:35, Marc Marí <marc.mari.barcelo@gmail.com>
> wrote:
> > I was fearing that answer :). No, I can't. I want to compare the
> > behaviour of a "normal" Linux 3.4 with another modified Linux 3.4,
> > and the second one is fixed.
> >
> > And is not that ancient, it only has 2.5 years :)
>
> In that case you'll need to debug the issue like you would
> any other "kernel misbehaving" issue -- figure out what the
> kernel is doing to cause it to print that message, identify
> whether that's because the kernel itself is buggy or because
> QEMU's hardware emulation is buggy, and go from there...
>
> There were a number of bugfixes applied to the versatile
> PCI controller code at some point after 3.4, so I wouldn't
> be very surprised if the answer turns out to be "this is
> just broken in 3.4".
>
> In particular, commit 9b0f7e39923 which isn't in 3.4 AFAIK
> basically says "we broke I/O access", which is probably what
> you're running into. I expect you'll need other fixes too.
>
> So you can try to find and cherry-pick the necessary fixes, which
> could be painful, or you can move to a newer kernel which already
> has them.
Thank you very much. I didn't know where to start looking, so I was
lost. This helps me find my way again.
Thanks
Marc
prev parent reply other threads:[~2015-01-13 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 9:05 [Qemu-devel] Linux 3.4, VersatilePB and PCI Marc Marí
2015-01-13 10:06 ` Peter Maydell
2015-01-13 10:35 ` Marc Marí
2015-01-13 10:46 ` Peter Maydell
2015-01-13 11:02 ` Marc Marí [this message]
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=20150113120229.2883a1e2@crunchbang \
--to=marc.mari.barcelo@gmail.com \
--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).