From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=36878 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PN5vA-0002ss-Fs for qemu-devel@nongnu.org; Mon, 29 Nov 2010 10:45:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PN5v9-00083A-1m for qemu-devel@nongnu.org; Mon, 29 Nov 2010 10:45:40 -0500 Received: from mail-qw0-f45.google.com ([209.85.216.45]:42444) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PN5v8-000830-Uz for qemu-devel@nongnu.org; Mon, 29 Nov 2010 10:45:39 -0500 Received: by qwh6 with SMTP id 6so206917qwh.4 for ; Mon, 29 Nov 2010 07:45:38 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 29 Nov 2010 15:45:37 +0000 Message-ID: Subject: Re: [Qemu-devel] qemu: hardware error: pl011_read: Bad offset 16000018 From: Prasad Joshi Content-Type: text/plain; charset=ISO-8859-1 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: qemu-devel@nongnu.org On Mon, Nov 29, 2010 at 3:13 PM, Peter Maydell wrote: > On 29 November 2010 14:37, Prasad Joshi wrote: >> I am running QEMU Arm emulation on x86_64 machine. I downloaded the >> arm-test kernel and the initrd image available on QEMU download site. >> >> When I run the qemu-system-arm with the memory less than or equal to >> 256M everything works fine. >> prasad@prasad-desktop:~/Downloads/arm-test$ qemu-system-arm -kernel >> zImage.integrator -initrd arm_root.img -m 256 >> >> But, when I assign memory more than 256M it fails to run > > This is because the Integrator development board only supports > a maximum of 256M of RAM (the hole in its physical address > layout for RAM is that large, and after that come some memory > mapped devices). > Thanks a lot Peter for your reply. I tried to emulate few other boards as well. IMHO, versatilepb supports more than 256M RAM, I guess it supports upto 512MB. But it too fails prasad@prasad-desktop:~/Downloads/arm_prasad$ qemu-system-arm -M versatilepb -kernel vmlinuz-2.6.26-2-versatile -initrd initrd.img-2.6.26-2-versatile -hda debian_lenny_arm_small.qcow2 -append "root=/dev/sda1" -m 512 qemu: hardware error: pl011_read: Bad offset 101f1018 CPU #0: R00=000133ed R01=101f1000 R02=00000055 R03=ffffffff R04=00008000 R05=00199430 R06=41069265 R07=00000183 R08=00000100 R09=00000000 R10=0017ff8c R11=00189418 R12=0018941c R13=0018940c R14=00013060 R15=00010afc PSR=200001d3 --C- A svc32 Aborted >> prasad@prasad-desktop:~/Downloads/arm-test$ qemu-system-arm -kernel >> zImage.integrator -initrd arm_root.img -m 512 >> qemu: hardware error: pl011_read: Bad offset 16000018 > > It's a bug that we don't do something sensible when the user > requests more memory than the board supports (like bailing > out with an error), rather than blindly mapping both RAM and > devices into the same place and then booting the kernel. > > (Slight tangent but related:) the interface to the board init > routine for "how much RAM should we model?" is a bit > limiting because there's no way to tell the difference between > "ram size specified by user on command line" and "ram size > which is a random default from vl.c". (It would be useful for > most boards models to default to whatever the maximum > standard amount of memory for them is, for instance.) > > Incidentally the Integrator is a truly ancient devboard and I'm > not sure it deserves to be the default any more ;-) > > -- PMM >