| 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
| ||
|
Message-ID: <1351736A-3DD7-4BE1-BF60-D95DFFEBA718@boeing.com> Date: Fri, 2 Jul 2010 19:20:07 -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: Re: [P2020] "Processor 1 is stuck" (introduced by 8b27f0b61) 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. 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/
Powered by blists - more mailing lists