From: jgq516@gmail.com
To: cyril@ti.com
Cc: linux-omap@vger.kernel.org
Subject: keystone2 board hangs with smp kernel
Date: Mon, 03 Jun 2013 10:18:51 +0800 [thread overview]
Message-ID: <51ABFD0B.3020701@gmail.com> (raw)
Hello Cyril,
I have got one TI keystone2 board, and tried different tags of tree:
git://arago-project.org/git/projects/linux-keystone.git,
but seems the kernel always hangs as follows, and kernel runs ok if add
"nosmp" flag.
[ 0.028386] CPU: Testing write buffer coherency: ok
[ 0.032493] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.037108] hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver,
7 counters available
[ 0.043763] Setting up static identity map for 0x80464628 - 0x8046465c
The uboot version which I used is from
git://arago-project.org/git/projects/u-boot-keystone.git
with tag DEV.MCSDK-2013-01.10, I also tried other tags, but seems no
different effect.
Could you give some advice about smp problem? Thanks in advance!
Regards,
Xiao
next reply other threads:[~2013-06-03 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 2:18 jgq516 [this message]
2013-06-03 2:33 ` keystone2 board hangs with smp kernel jgq516
2013-06-03 3:47 ` jgq516
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=51ABFD0B.3020701@gmail.com \
--to=jgq516@gmail.com \
--cc=cyril@ti.com \
--cc=linux-omap@vger.kernel.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