From: florian@openwrt.org (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM realview breakages w/ 3.7 under qemu
Date: Thu, 13 Dec 2012 18:55:47 +0100 [thread overview]
Message-ID: <50CA16A3.4020108@openwrt.org> (raw)
In-Reply-To: <20121213174817.GB12946@mudshark.cambridge.arm.com>
Le 12/13/12 18:48, Will Deacon a ?crit :
> On Thu, Dec 13, 2012 at 05:26:25PM +0000, Florian Fainelli wrote:
>> Hi,
> Hi Florian,
>
>> I am experiencing several issues with the ARM RealView platform under qemu:
>>
>> 1) The RealView EB MP-Core is stuck in the timer calibration, this
>> isssue was already present in all 3.6 kernels, and I have not yet been
>> able to find the root cause of this. PBX A9 with the same kernel binary
>> works flawlessly.
> Can you try picking 810883f05982 ("ARM: 7594/1: Add .smp entry for
> REALVIEW_EB") please?
I picked that up and it did not make any difference we are still stuck
calibrating the timer.
>
>> 2) There are some strange things happening with the RAM on these
>> platforms too, for instance:
>>
>> - EB MP-Core: booting with 128MBytes of RAM does not work, booting with
>> more than 256Mbytes results in the amount of RAM seen by the kernel
>> truncated to 256Mbytes
>>
>> - PBX A9: booting with less than 1024MBytes of RAM causes this:
>> [ 0.000000] Truncating RAM at 20000000-3fffffff to -3f7fffff (vmalloc
>> region overlap).
>> [ 0.000000] Ignoring RAM at 80000000-8fffffff (vmalloc region overlap).
>>
>> Do these issues sounds familiar to any of you? The kernel config is
>> attached in case that helps.
> I'm afraid these memory issues don't ring any bells with me, but I do
> actually have hardware for EB MP and PBX so I can see if that works with
> your .config (although you may have to wait until next week).
>
> Can you provide your command lines please? I'm also assuming you're using
> 3.7?
The qemu command-line is the following:
qemu-system-arm -M realview-eb-mpcore -kernel
bin/realview/openwrt-realview-vmlinux.elf -nographic -m 768 -append
"earlyprintk console=ttyAMA0"
And the kernel command-line is:
console=ttyAMA0 mem=128M
CMDLINE_FROM_BOOTLOADER is set, so only the command-line from qemu
actually matters.
Thanks!
--
Florian
next prev parent reply other threads:[~2012-12-13 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 17:26 ARM realview breakages w/ 3.7 under qemu Florian Fainelli
2012-12-13 17:48 ` Will Deacon
2012-12-13 17:55 ` Florian Fainelli [this message]
2012-12-14 9:40 ` Russell King - ARM Linux
2012-12-14 10:37 ` Florian Fainelli
2012-12-14 10:47 ` Russell King - ARM Linux
2012-12-14 10:50 ` Florian Fainelli
2012-12-17 13:42 ` Will Deacon
2012-12-17 14:06 ` Florian Fainelli
2012-12-17 15:13 ` Will Deacon
2012-12-17 15:23 ` Florian Fainelli
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=50CA16A3.4020108@openwrt.org \
--to=florian@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.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.