From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: Commit 384a290283fde63ba8dc671fca5420111cdac19a seems to break 11MPCore boot
Date: Wed, 30 Jan 2013 16:05:36 +0000 [thread overview]
Message-ID: <1359561936.3094.19.camel@hornet> (raw)
In-Reply-To: <alpine.LFD.2.02.1301301050230.6300@xanadu.home>
On Wed, 2013-01-30 at 16:00 +0000, Nicolas Pitre wrote:
> > Pawel suggested I try reverting 384a290283fde63ba8dc671fca5420111cdac19a -
> > "ARM: gic: use a private mapping for CPU target interfaces" that you've
> > authored. With this commit reverted the kernel boots.
> >
> > I am not quite sure why the commit breaks 11MPCore but Pawel (cc'd) might be
> > able to shed light on that.
>
> That would be appreciated as I don't have any good answer to provide.
Uh, I afraid that my light-generating capabilities may be slightly
overestimated, as it was just a logical but lucky guess, really.
> Typically, this patch highlighted problems with bad holding pen
> implementations where secondary CPUs would enter the kernel all at the
> same time. In that case the kernel was crashing even before displaying
> "CPU2: Booted secondary processor".
I'll try to get the board and reproduce the problem, but I can't promise
any dates...
Pawe?
next prev parent reply other threads:[~2013-01-30 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 15:23 Commit 384a290283fde63ba8dc671fca5420111cdac19a seems to break 11MPCore boot Punit Agrawal
2013-01-30 16:00 ` Nicolas Pitre
2013-01-30 16:05 ` Pawel Moll [this message]
2013-01-30 16:21 ` Russell King - ARM Linux
2013-01-30 16:45 ` Russell King - ARM Linux
2013-01-30 17:19 ` Russell King - ARM Linux
2013-01-30 17:30 ` Nicolas Pitre
2013-01-30 17:57 ` Will Deacon
2013-01-30 18:03 ` Russell King - ARM Linux
2013-01-30 18:16 ` Russell King - ARM Linux
2013-01-30 18:19 ` Russell King - ARM Linux
2013-01-30 20:30 ` Russell King - ARM Linux
2013-01-30 21:02 ` Nicolas Pitre
2013-01-30 16:04 ` Lorenzo Pieralisi
2013-01-30 16:40 ` Punit Agrawal
2013-01-30 16:56 ` Lorenzo Pieralisi
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=1359561936.3094.19.camel@hornet \
--to=pawel.moll@arm.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).