From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41132)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <marc.mari.barcelo@gmail.com>) id 1YAxPm-0007nC-Vx
	for qemu-devel@nongnu.org; Tue, 13 Jan 2015 04:05:31 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <marc.mari.barcelo@gmail.com>) id 1YAxPi-0005mB-Pt
	for qemu-devel@nongnu.org; Tue, 13 Jan 2015 04:05:30 -0500
Received: from mail-we0-x230.google.com ([2a00:1450:400c:c03::230]:45905)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <marc.mari.barcelo@gmail.com>) id 1YAxPi-0005lH-IN
	for qemu-devel@nongnu.org; Tue, 13 Jan 2015 04:05:26 -0500
Received: by mail-we0-f176.google.com with SMTP id w61so1585691wes.7
	for <qemu-devel@nongnu.org>; Tue, 13 Jan 2015 01:05:25 -0800 (PST)
Received: from crunchbang (201.Red-83-59-87.dynamicIP.rima-tde.net.
	[83.59.87.201]) by mx.google.com with ESMTPSA id
	cp4sm24845494wjb.16.2015.01.13.01.05.24 for <qemu-devel@nongnu.org>
	(version=SSLv3 cipher=RC4-SHA bits=128/128);
	Tue, 13 Jan 2015 01:05:25 -0800 (PST)
Date: Tue, 13 Jan 2015 10:05:21 +0100
From: Marc =?UTF-8?B?TWFyw60=?= <marc.mari.barcelo@gmail.com>
Message-ID: <20150113100521.3f735c65@crunchbang>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Linux 3.4, VersatilePB and PCI
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel <qemu-devel@nongnu.org>

Hi

In short:
I have a Linux 3.4 kernel on top of a VersatilePB machine that
fails to mount root file system with message:

sym53c8xx 0000:00:0c.0: BAR 0: can't reserve [io 0x44000000-0x440000ff]

after booting with:

qemu-system-arm -M versatilepb -serial telnet::4444,server -kernel
vmlinuz-3.4.0 -initrd initrd.img-3.4.0 -hda hda.img -hdb hdb.img
-append "console=ttyAMA0 root=/dev/sda1"

In long:
I have a VersatilePB machine with Debian and Linux 3.2 on top. I
downloaded Linux 3.4 and, inside the machine (no cross-compilation, to
avoid any little issues), I copied the actual 3.2 config to the new
kernel, run menuconfig, just changed SCSI ACARD support (because it
does not compile in 3.4) and kernel compression to GZIP, and run
make-kpkg --initrd kernel_image (Debian-specific tools, to avoid any
little issues). When it finished, I installed the resulting .deb, and
in the host I copied the /boot/vmlinuz-3.4.0 and the /boot/initrd-3.4.0
from the guest, and tried to boot again. Initrd will fail to mount root
file system with the message above.

But if I do exactly the same process with a Linux 3.2.0 it does work.

Am I doing something wrong with the kernels? Or is this a bug either in
QEMU or Linux? I'd like a bit of help in, at least, knowing if the
error is anything related with QEMU.

Thanks
Marc