From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 877E6C433ED for ; Thu, 22 Apr 2021 05:26:29 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0DE9F61448 for ; Thu, 22 Apr 2021 05:26:29 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0DE9F61448 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bugs.launchpad.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:59180 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lZRr9-0000sD-Cf for qemu-devel@archiver.kernel.org; Thu, 22 Apr 2021 01:26:27 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:58594) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lZRpd-00083F-VI for qemu-devel@nongnu.org; Thu, 22 Apr 2021 01:24:53 -0400 Received: from indium.canonical.com ([91.189.90.7]:49556) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lZRpc-0001FN-8P for qemu-devel@nongnu.org; Thu, 22 Apr 2021 01:24:53 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1lZRpa-0002Si-E7 for ; Thu, 22 Apr 2021 05:24:50 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 698502E815D for ; Thu, 22 Apr 2021 05:24:50 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 22 Apr 2021 05:13:33 -0000 From: Thomas Huth <1596832@bugs.launchpad.net> To: qemu-devel@nongnu.org X-Launchpad-Notification-Type: bug X-Launchpad-Bug: product=qemu; status=Incomplete; importance=Undecided; assignee=None; X-Launchpad-Bug-Tags: ppc X-Launchpad-Bug-Information-Type: Public X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Bug-Commenters: andree182 ecsdn th-huth X-Launchpad-Bug-Reporter: Andrej Krutak (andree182) X-Launchpad-Bug-Modifier: Thomas Huth (th-huth) References: <20160628075027.23593.17849.malonedeb@gac.canonical.com> Message-Id: <161906841386.32404.14124644574995656107.malone@soybean.canonical.com> Subject: [Bug 1596832] Re: e500 -bios/-kernel broken with big images X-Launchpad-Message-Rationale: Subscriber (QEMU) @qemu-devel-ml X-Launchpad-Message-For: qemu-devel-ml Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="1552fceb1603b3da6cfa437575d9c9fc4b2e683a"; Instance="production" X-Launchpad-Hash: b9cbcc879c94eb49430810a86d46d8f261f4c829 Received-SPF: none client-ip=91.189.90.7; envelope-from=bounces@canonical.com; helo=indium.canonical.com X-Spam_score_int: -65 X-Spam_score: -6.6 X-Spam_bar: ------ X-Spam_report: (-6.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Bug 1596832 <1596832@bugs.launchpad.net> Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now. If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or please mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience. ** Changed in: qemu Status: New =3D> Incomplete -- = 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: Incomplete 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