From: ilya@compulab.co.il (Ilya Ledvich)
To: linux-arm-kernel@lists.infradead.org
Subject: iMX7d cpu1 issue
Date: Tue, 16 Feb 2016 09:56:47 +0200 [thread overview]
Message-ID: <56C2D63F.1030408@compulab.co.il> (raw)
Hi Shawn,
I'm working on Compulab CL-SOM-IMX7 device
(http://www.compulab.co.il/products/computer-on-modules/cl-som-imx7-freescale-i-mx-7-system-on-module)
based on Freescale iMX7d CPU.
I use the Freescale latest BSP imx_3.14.52_1.1.0_ga and the Linux
mainline v4.4-rc6 as a reference.
I observe an issue with bringing up the second CPU core. Briefly, the
kernel can successfully boot only when CPU1 fails to come online.
In this case the boot log shows the following messages:
...
CPU1: failed to come online
Brought up 1 CPUs
SMP: Total of 1 processors activated (6.00 BogoMIPS).
...
Otherwise, the device tries to start kernel several times until the boot
process eventually crashes. Please see attached logs for more details.
This never happens on mainline Linus kernel, because it never tries to
bring up CPU1.
Unfortunately, we cannot verify this behavior on reference board cause
we have no one.
Have you ever seen such behavior? Could you please advice something?
Kind regards,
Ilya.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cl-som-imx7-boot-ok.log
Type: text/x-log
Size: 14933 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160216/fb57af9a/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cl-som-imx7-boot-failed.log
Type: text/x-log
Size: 21571 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160216/fb57af9a/attachment-0003.bin>
next reply other threads:[~2016-02-16 7:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 7:56 Ilya Ledvich [this message]
2016-02-18 14:09 ` iMX7d cpu1 issue Shawn Guo
2016-02-18 15:15 ` Yongcai Huang
2016-02-18 16:33 ` Ilya Ledvich
2016-02-18 15:24 ` Frank Li
2016-02-18 16:44 ` Ilya Ledvich
2016-02-18 16:56 ` Frank Li
2016-02-19 8:11 ` Ilya Ledvich
2016-02-21 15:22 ` Fabio Estevam
2016-02-22 10:53 ` Ilya Ledvich
2016-02-22 20:48 ` Frank Li
2016-02-22 20:59 ` Fabio Estevam
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=56C2D63F.1030408@compulab.co.il \
--to=ilya@compulab.co.il \
--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).