linux-kernel - [P2020] "Processor 1 is stuck" (introduced by 8b27f0b61)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 2 Jul 2010 18:30:47 -0500
From:	"Moffett, Kyle D" <Kyle.D.Moffett@...ing.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	Kumar Gala <galak@...nel.crashing.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Kyle D Moffett <kyle@...fetthome.net>
Subject: [P2020] "Processor 1 is stuck" (introduced by 8b27f0b61)

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@...nel.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/