linux-kernel - Re: [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-prev] [day] [month] [year] [list]

Message-ID: <AANLkTimeWqEoqreMM-7oALWuv5QbT0aPn8bU6NOs_-l4@mail.gmail.com>
Date:	Sat, 3 Jul 2010 10:25:50 -0400
From:	Kyle Moffett <kyle@...fetthome.net>
To:	"Moffett, Kyle D" <Kyle.D.Moffett@...ing.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Kumar Gala <galak@...nel.crashing.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [P2020] "Processor 1 is stuck" (introduced by 8b27f0b61)

On Fri, Jul 2, 2010 at 20:20, Moffett, Kyle D <Kyle.D.Moffett@...ing.com> wrote:
> On Jul 02, 2010, at 19:30, Moffett, Kyle D wrote:
>> 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.
>>
>> [...]
>>
>> 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
>
> With a little bit more debugging, I was able to strip the patch down to a partial revert (on top of v2.6.34) which seems to fix the bug here.  I pushed that patch out to the "latest-v2.6.34" branch of linux.git as commit 1214341.

Aha!

I just found Kumar's upstream commit
78f622377f7d31d988db350a43c5689dd5f31876 (which seems to have been
sent to the stable trees as well), which converts loadcam_entry() back
into being an assembly function because it breaks ftrace.  I believe
my config has ftrace on, which would explain the problem.

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/