From: Launchpad Bug Tracker <1596832@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1596832] Re: e500 -bios/-kernel broken with big images
Date: Tue, 22 Jun 2021 04:17:39 -0000 [thread overview]
Message-ID: <162433546014.20423.887240255658140427.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20160628075027.23593.17849.malonedeb@gac.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1596832
Title:
e500 -bios/-kernel broken with big images
Status in QEMU:
Expired
Bug description:
This is tested using qemu 2.4.1, but it looks like the code
qemu/hw/ppc/e500.c has not changed since. This looks like the source
of the problem:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=3812c71ffaa2cf733c3087792b859fef30b7545f
What works:
----------
Basic invocation qemu-system-ppc -machine ppce500 -monitor stdio
-bios u-boot.e500 works, I get the uboot prompt and this:
(qemu) info roms
addr=0000000000f00000 size=0x044b8c mem=ram name="phdr #0: .../qemu/share/qemu/u-boot.e500"
addr=0000000000f81000 size=0x006b00 mem=ram name="phdr #1: .../qemu/share/qemu/u-boot.e500"
Passing u-boot.e500 image as kernel (-bios u-boot.e500 -kernel u-boot.e500) appears to work, $qemu_kernel_addr is filled in, though (as expected) uboot complains about the image format.
(qemu) info roms
addr=0000000000f00000 size=0x044b8c mem=ram name="phdr #0: .../qemu/share/qemu/u-boot.e500"
addr=0000000000f81000 size=0x006b00 mem=ram name="phdr #1: .../qemu/share/qemu/u-boot.e500"
addr=0000000002000000 size=0x054e8c mem=ram name=".../qemu/share/qemu/u-boot.e500
What doesn't work:
-----------------
However, once I try to load a big image (>=32 MiB), uboot doesn't even
show anything:
qemu-system-ppc -machine ppce500 -monitor stdio -bios u-boot.e500
-kernel boot/vmlinux -m 1024
(qemu) info roms
addr=0000000000f00000 size=0x044b8c mem=ram name="phdr #0: .../qemu/share/qemu/u-boot.e500"
addr=0000000000f81000 size=0x006b00 mem=ram name="phdr #1: .../qemu/share/qemu/u-boot.e500"
addr=0000000002000000 size=0x27aeedc mem=ram name="boot/vmlinux"
...
(gdb) bt
#0 0x00f2efcc in ?? ()
#1 0x00f31554 in ?? ()
#2 0x00f03f4c in ?? ()
#3 0x00f04458 in ?? ()
#4 0x00f028dc in ?? ()
#5 0x00f01080 in ?? ()
The thing is, this used to work +- before the commit, where I'd just
pass the image as -kernel option, and it booted.
If I do that now (w/o the -bios option, using the exact same image), the kernel gets loaded twice, only at different addresses (the cause is obvious from the commit), causing overlap error:
qemu-system-ppc -machine ppce500 -monitor stdio -kernel boot/vmlinux -m 1024
QEMU 2.4.1 monitor - type 'help' for more information
(qemu) rom: requested regions overlap (rom boot/vmlinux. free=0x00000000027492fc, addr=0x0000000002000000)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1596832/+subscriptions
prev parent reply other threads:[~2021-06-22 5:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 7:50 [Qemu-devel] [Bug 1596832] [NEW] e500 -bios/-kernel broken with big images Andrej Krutak
2016-06-28 8:26 ` [Qemu-devel] [Bug 1596832] " T. Huth
2019-12-18 21:45 ` ecsdn
2021-04-22 5:13 ` Thomas Huth
2021-06-22 4:17 ` Launchpad Bug Tracker [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=162433546014.20423.887240255658140427.malone@loganberry.canonical.com \
--to=1596832@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.