From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46808) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHns2-0000GN-PV for qemu-devel@nongnu.org; Tue, 28 Jun 2016 03:55:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bHnry-0004ZT-Lt for qemu-devel@nongnu.org; Tue, 28 Jun 2016 03:55:45 -0400 Received: from indium.canonical.com ([91.189.90.7]:43421) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHnry-0004ZP-D4 for qemu-devel@nongnu.org; Tue, 28 Jun 2016 03:55:42 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1bHnrx-0007Ob-IQ for ; Tue, 28 Jun 2016 07:55:41 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 680D62E80C9 for ; Tue, 28 Jun 2016 07:55:41 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 28 Jun 2016 07:50:27 -0000 From: Andrej Krutak <1596832@bugs.launchpad.net> Reply-To: Bug 1596832 <1596832@bugs.launchpad.net> Sender: bounces@canonical.com Message-Id: <20160628075027.23593.17849.malonedeb@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1596832] [NEW] e500 -bios/-kernel broken with big images List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Public bug reported: 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=3Dqemu.git;a=3Dcommitdiff;h=3D3812c71ffaa2cf733c3087= 792b859fef30b7545f 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=3D0000000000f00000 size=3D0x044b8c mem=3Dram name=3D"phdr #0: .../qemu= /share/qemu/u-boot.e500" addr=3D0000000000f81000 size=3D0x006b00 mem=3Dram name=3D"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) uboo= t complains about the image format. (qemu) info roms addr=3D0000000000f00000 size=3D0x044b8c mem=3Dram name=3D"phdr #0: .../qemu= /share/qemu/u-boot.e500" addr=3D0000000000f81000 size=3D0x006b00 mem=3Dram name=3D"phdr #1: .../qemu= /share/qemu/u-boot.e500" addr=3D0000000002000000 size=3D0x054e8c mem=3Dram name=3D".../qemu/share/qe= mu/u-boot.e500 What doesn't work: ----------------- However, once I try to load a big image (>=3D32 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=3D0000000000f00000 size=3D0x044b8c mem=3Dram name=3D"phdr #0: .../qemu= /share/qemu/u-boot.e500" addr=3D0000000000f81000 size=3D0x006b00 mem=3Dram name=3D"phdr #1: .../qemu= /share/qemu/u-boot.e500" addr=3D0000000002000000 size=3D0x27aeedc mem=3Dram name=3D"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 ke= rnel gets loaded twice, only at different addresses (the cause is obvious f= rom the commit), causing overlap error: qemu-system-ppc -machine ppce500 -monitor stdio -kernel boot/vmlinux -m 1= 024 QEMU 2.4.1 monitor - type 'help' for more information (qemu) rom: requested regions overlap (rom boot/vmlinux. free=3D0x000000000= 27492fc, addr=3D0x0000000002000000) ** Affects: qemu Importance: Undecided Status: New -- = 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: New 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=3Dqemu.git;a=3Dcommitdiff;h=3D3812c71ffaa2cf733c30= 87792b859fef30b7545f = 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=3D0000000000f00000 size=3D0x044b8c mem=3Dram name=3D"phdr #0: .../qe= mu/share/qemu/u-boot.e500" addr=3D0000000000f81000 size=3D0x006b00 mem=3Dram name=3D"phdr #1: .../qe= mu/share/qemu/u-boot.e500" = Passing u-boot.e500 image as kernel (-bios u-boot.e500 -kernel u-boot.e50= 0) appears to work, $qemu_kernel_addr is filled in, though (as expected) ub= oot complains about the image format. (qemu) info roms addr=3D0000000000f00000 size=3D0x044b8c mem=3Dram name=3D"phdr #0: .../qe= mu/share/qemu/u-boot.e500" addr=3D0000000000f81000 size=3D0x006b00 mem=3Dram name=3D"phdr #1: .../qe= mu/share/qemu/u-boot.e500" addr=3D0000000002000000 size=3D0x054e8c mem=3Dram name=3D".../qemu/share/= qemu/u-boot.e500 What doesn't work: ----------------- However, once I try to load a big image (>=3D32 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=3D0000000000f00000 size=3D0x044b8c mem=3Dram name=3D"phdr #0: .../qe= mu/share/qemu/u-boot.e500" addr=3D0000000000f81000 size=3D0x006b00 mem=3Dram name=3D"phdr #1: .../qe= mu/share/qemu/u-boot.e500" addr=3D0000000002000000 size=3D0x27aeedc mem=3Dram name=3D"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=3D0x0000000= 0027492fc, addr=3D0x0000000002000000) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1596832/+subscriptions