From: ayankumarh@gmail.com (AYAN KUMAR HALDER)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel booting stuck at "CPU1: Booted secondary processor"
Date: Tue, 17 Mar 2015 11:44:44 +0530 [thread overview]
Message-ID: <CAGAs2AkU=mGxjm1sLNiSqD7yvxROUxRrqqN0z4QBrPCRkdnVvg@mail.gmail.com> (raw)
Hi,
I am porting kernel (3.14.22) on a custom ARM(Cortex A9 x 3) based platform.
I was able to get it working on uniprocessor mode.
Now I wish to get the SMP mode working as mine is Cortex A9 x3 platform.
However, I see that the booting gets stuck after the following log:-
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x1f9690 - 0x1f96c4
CPU1: Booted secondary processor
When I debugged it further, I found that it waits endlessly in a
arch_spin_lock() :-
while (lockval.tickets.next != lockval.tickets.owner) { // loops here
wfe();
lockval.tickets.owner = ACCESS_ONCE(lock->tickets.owner);
}
It would be great if someone can give me pointers about how to proceed ahead.
Regards,
Ayan kumar Halder
next reply other threads:[~2015-03-17 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 6:14 AYAN KUMAR HALDER [this message]
2015-03-17 9:44 ` Kernel booting stuck at "CPU1: Booted secondary processor" Arun KS
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='CAGAs2AkU=mGxjm1sLNiSqD7yvxROUxRrqqN0z4QBrPCRkdnVvg@mail.gmail.com' \
--to=ayankumarh@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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.