qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Marc Marí" <marc.mari.barcelo@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Linux 3.4, VersatilePB and PCI
Date: Tue, 13 Jan 2015 10:05:21 +0100	[thread overview]
Message-ID: <20150113100521.3f735c65@crunchbang> (raw)

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

             reply	other threads:[~2015-01-13  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13  9:05 Marc Marí [this message]
2015-01-13 10:06 ` [Qemu-devel] Linux 3.4, VersatilePB and PCI Peter Maydell
2015-01-13 10:35   ` Marc Marí
2015-01-13 10:46     ` Peter Maydell
2015-01-13 11:02       ` Marc Marí

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=20150113100521.3f735c65@crunchbang \
    --to=marc.mari.barcelo@gmail.com \
    --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).