From: trblinux@gmail.com (Tushar Behera)
To: linux-arm-kernel@lists.infradead.org
Subject: mainline boot: 64 boots: 62 pass, 2 fail (v3.16-rc1-2-gebe0618)
Date: Fri, 27 Jun 2014 08:36:42 +0530 [thread overview]
Message-ID: <53ACDFC2.5020206@gmail.com> (raw)
In-Reply-To: <53AC77A2.4090207@codeaurora.org>
On 06/27/2014 01:12 AM, Laura Abbott wrote:
>
> +static unsigned int bank_cnt;
> +static unsigned int max_cnt;
> +
> int __init arm_add_memory(u64 start, u64 size)
> {
> u64 aligned_start;
>
> /*
> + * Some buggy bootloaders rely on the old meminfo behavior of not adding
> + * more than n banks since anything past that may contain invalid data.
> + */
> + if (bank_cnt >= max_cnt) {
> + pr_crit("Max banks too low, ignoring memory at 0x%08llx\n",
> + (long long)start);
> + return -EINVAL;
> + }
> +
> + bank_cnt++;
> +
> + /*
> * Ensure that start/size are aligned to a page boundary.
> * Size is appropriately rounded down, start is rounded up.
> */
> @@ -879,6 +894,7 @@ void __init setup_arch(char **cmdline_p)
> mdesc = setup_machine_tags(__atags_pointer, __machine_arch_type);
> machine_desc = mdesc;
> machine_name = mdesc->name;
> + max_cnt = mdesc->bank_limit;
arm_add_memory is getting called before this is being set, resulting in
none of the memory banks getting added[1].
setup_machine_fdt -> early_init_dt_scan -> early_init_dt_scan_memory
Would it make sense to re-introduce the config option ARM_NR_BANKS and
replace max_cnt with NR_BANKS?
[1] http://pastebin.com/MawYD7kb
>
> if (mdesc->reboot_mode != REBOOT_HARD)
> reboot_mode = mdesc->reboot_mode;
> diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
> index f38cf7c..91283fd 100644
> --- a/arch/arm/mach-exynos/exynos.c
> +++ b/arch/arm/mach-exynos/exynos.c
> @@ -350,4 +350,5 @@ DT_MACHINE_START(EXYNOS_DT, "SAMSUNG EXYNOS (Flattened Device Tree)")
> .dt_compat = exynos_dt_compat,
> .restart = exynos_restart,
> .reserve = exynos_reserve,
> + .bank_limit = 8,
> MACHINE_END
>
--
Tushar Behera
next prev parent reply other threads:[~2014-06-27 3:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <539fdd37.e7bc420a.76b9.ffffb583@mx.google.com>
[not found] ` <CAGa+x85nqPbH-sye28ni=gUEdgjGdUDqHhv1+0pV5aO8y1+wHQ@mail.gmail.com>
[not found] ` <53A106F1.10201@gmail.com>
[not found] ` <CAGa+x8527FEPk6fg5kv-fbOzK3MzcFooFGE9Me12b9C_Pv=UzA@mail.gmail.com>
[not found] ` <53A2AE11.2050208@gmail.com>
[not found] ` <53A2BE94.2010308@gmail.com>
2014-06-23 3:56 ` mainline boot: 64 boots: 62 pass, 2 fail (v3.16-rc1-2-gebe0618) Tushar Behera
2014-06-23 18:32 ` Kevin Hilman
2014-06-24 17:47 ` Laura Abbott
2014-06-24 22:29 ` Laura Abbott
2014-06-25 12:13 ` Tushar Behera
2014-06-25 21:57 ` Laura Abbott
2014-06-26 6:44 ` Tushar Behera
2014-06-26 14:59 ` Kevin Hilman
2014-06-26 15:17 ` Russell King - ARM Linux
2014-06-26 19:42 ` Laura Abbott
2014-06-27 3:06 ` Tushar Behera [this message]
2014-06-27 9:09 ` Laura Abbott
2014-06-27 9:40 ` Russell King - ARM Linux
2014-06-26 17:04 ` Andreas Färber
2014-06-27 3:28 ` Tushar Behera
2014-06-25 2:07 ` Andreas Färber
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=53ACDFC2.5020206@gmail.com \
--to=trblinux@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).