From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: SoCFPGA with CONFIG_THUMB2_KERNEL boot error
Date: Thu, 21 Apr 2016 08:54:10 +0200 [thread overview]
Message-ID: <20160421065410.GA21638@pengutronix.de> (raw)
In-Reply-To: <5717A67C.4010007@opensource.altera.com>
On Wed, Apr 20, 2016 at 10:55:40AM -0500, Dinh Nguyen wrote:
> > void __init socfpga_sysmgr_init(void)
> > {
> > @@ -38,14 +37,6 @@ void __init socfpga_sysmgr_init(void)
> >
> > np = of_find_compatible_node(NULL, NULL, "altr,sys-mgr");
> >
> > - if (of_property_read_u32(np, "cpu1-start-addr",
> > - (u32 *) &socfpga_cpu1start_addr))
> > - pr_err("SMP: Need cpu1-start-addr in device tree.\n");
> > -
> > - /* Ensure that socfpga_cpu1start_addr is visible to other CPUs */
> > - smp_wmb();
> > - sync_cache_w(&socfpga_cpu1start_addr);
> > -
> > sys_manager_base_addr = of_iomap(np, 0);
> >
> > np = of_find_compatible_node(NULL, NULL, "altr,rst-mgr");
> >
>
> Your proposed patch is causing this failure during a CPU hotlpug, and
> ultimately CPU1 doesn't seem to be able to comeback online at all:
>
> # echo 0 > /sys/devices/system/cpu/cpu1/online
> [ 53.664085] CPU1: shutdown
> # echo 1 > /sys/devices/system/cpu/cpu1/online
>
> [ 60.394169] Unable to handle kernel paging request at virtual address
> c0118668
This issue can be fixed by setting the socfpga_boot_fn variable in the
smp_prepare_cpus hook instead of the smp_boot_secondary hook. I just
a fixed version as a formal patch. Compared to the last version I also
removed the unnecessary if(1) and fixed big endian support.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2016-04-21 6:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 14:02 SoCFPGA with CONFIG_THUMB2_KERNEL boot error Steffen Trumtrar
2016-04-20 9:25 ` Dave Martin
2016-04-20 9:39 ` Ard Biesheuvel
2016-04-20 9:43 ` Ard Biesheuvel
2016-04-20 9:55 ` Sascha Hauer
2016-04-20 10:26 ` Ard Biesheuvel
2016-04-20 11:00 ` Sascha Hauer
2016-04-20 11:06 ` Ard Biesheuvel
2016-04-20 23:51 ` Russell King - ARM Linux
2016-04-21 6:24 ` Ard Biesheuvel
2016-04-21 7:52 ` Ard Biesheuvel
2016-04-20 11:06 ` Sascha Hauer
2016-04-20 15:55 ` Dinh Nguyen
2016-04-21 6:54 ` Sascha Hauer [this message]
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=20160421065410.GA21638@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).