From: "Moffett, Kyle D" <Kyle.D.Moffett@boeing.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Kumar Gala <galak@kernel.crashing.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Kyle D Moffett <kyle@moffetthome.net>
Subject: [P2020] "Processor 1 is stuck" (introduced by 8b27f0b61)
Date: Fri, 2 Jul 2010 18:30:47 -0500 [thread overview]
Message-ID: <BAD2EBFA-91F7-478B-8BA8-F7A099050A2F@boeing.com> (raw)
Hello,
I'm working on a new board port to a P2020-based system (e500v2) and I appear to be hitting a regression which causes the second core to fail to come up at boot with a "Processor 1 is stuck" message.
In the successful case (my board support patches on top of v2.6.32):
> smp_85xx_kick_cpu: kick CPU #1
> smp_85xx_kick_cpu: cpu-release-addr: 0x7ffff280
> smp_85xx_kick_cpu: got virt addr: 0xf1014280
> waited 1 msecs for CPU #1
> Processor 1 found.
> Brought up 2 CPUs
In the failing case (with board support patches on top of either 8b27f0b61 or v2.6.34):
> smp_85xx_kick_cpu: kick CPU #1
> smp_85xx_kick_cpu: cpu-release-addr: 0x7ffff280
> smp_85xx_kick_cpu: got virt addr: 0xf1014280
> waited 1 msecs for CPU #1
> [...5 second delay here...]
> Processor 1 is stuck.
> Brought up 1 CPUs
I believe I've bisected a bug to this commit:
> Commit: 8b27f0b61db57f5555fc2d3fc95c3ea9fd1a9d6c
> Author: Kumar Gala <galak@kernel.crashing.org>
>
> powerpc/fsl-booke: Rework TLB CAM code
> * Bump'd # of CAM entries to 64 to support e500mc
> * Make the code handle MAS7 properly
> * Use pr_cont instead of creating a string as we go
If I revert 8b27f0b61 on top of v2.6.34 (I fixed the conflicts by deleting the extra hunks), both CPUs come up properly. My current board support files can be browsed via gitweb or cloned via smart-http or natively from here:
http://opensource.exmeritus.com/git/hww-1u-1a/linux.git
git://opensource.exmeritus.com/hww-1u-1a/linux.git
The "latest-v2.6.34" branch is based on v2.6.34 and does not work (Processor 1 is stuck), the "latest-v2.6.32" branch is based on v2.6.32.15 and works correctly.
Our U-Boot port can be browsed here:
http://opensource.exmeritus.com/git/hww-1u-1a/u-boot.git
git://opensource.exmeritus.com/hww-1u-1a/u-boot.git
Any help you can provide would be greatly appreciated.
Cheers,
Kyle Moffett
next reply other threads:[~2010-07-02 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 23:30 Moffett, Kyle D [this message]
2010-07-03 0:20 ` Moffett, Kyle D
2010-07-03 14:25 ` Kyle Moffett
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=BAD2EBFA-91F7-478B-8BA8-F7A099050A2F@boeing.com \
--to=kyle.d.moffett@boeing.com \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=kyle@moffetthome.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®