From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36351) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAzFD-0004IM-9H for qemu-devel@nongnu.org; Tue, 13 Jan 2015 06:02:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YAzF5-0005FA-Gy for qemu-devel@nongnu.org; Tue, 13 Jan 2015 06:02:43 -0500 Received: from mail-wg0-x22b.google.com ([2a00:1450:400c:c00::22b]:41390) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YAzF5-0005Ep-AR for qemu-devel@nongnu.org; Tue, 13 Jan 2015 06:02:35 -0500 Received: by mail-wg0-f43.google.com with SMTP id k14so2202633wgh.2 for ; Tue, 13 Jan 2015 03:02:34 -0800 (PST) Date: Tue, 13 Jan 2015 12:02:29 +0100 From: Marc =?UTF-8?B?TWFyw60=?= Message-ID: <20150113120229.2883a1e2@crunchbang> In-Reply-To: References: <20150113100521.3f735c65@crunchbang> <20150113113535.4b0d2e42@crunchbang> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Linux 3.4, VersatilePB and PCI List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: qemu-devel El Tue, 13 Jan 2015 10:46:20 +0000 Peter Maydell escribi=C3=B3: > On 13 January 2015 at 10:35, Marc Mar=C3=AD > 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 :) >=20 > 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... >=20 > 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". >=20 > 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. >=20 > 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