From owner-freebsd-ppc@FreeBSD.ORG Tue Jun 5 22:09:52 2012 Return-Path: Delivered-To: powerpc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA12C1065672 for ; Tue, 5 Jun 2012 22:09:52 +0000 (UTC) (envelope-from marcelm@juniper.net) Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by mx1.freebsd.org (Postfix) with ESMTP id 898CA8FC18 for ; Tue, 5 Jun 2012 22:09:52 +0000 (UTC) Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKT86DsPJWPQRfTBbPwDI/mWp7ViDu1rkN@postini.com; Tue, 05 Jun 2012 15:09:52 PDT Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 5 Jun 2012 15:07:41 -0700 From: Marcel Moolenaar To: Rafal Jaworowski Date: Tue, 5 Jun 2012 15:07:40 -0700 Thread-Topic: [P2020] FreeBSD cannot enable 2nd core. Thread-Index: Ac1DZ6AtGhpQkSsDTLm2T7Z6wY5KJw== Message-ID: References: <9F7F498C-22D3-4D6D-8242-019FB36B998A@juniper.net> <04DDA357-B2ED-4656-80BD-8FA436759EEF@semihalf.com> In-Reply-To: <04DDA357-B2ED-4656-80BD-8FA436759EEF@semihalf.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "powerpc@freebsd.org" Subject: Re: [P2020] FreeBSD cannot enable 2nd core. X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 22:09:52 -0000 On Jun 5, 2012, at 12:51 PM, Rafal Jaworowski wrote: >=20 > On 2012-06-02, at 17:21, Marcel Moolenaar wrote: >=20 >> All, >>=20 >> I'm running into a weird issue where the 2nd core of a P2020 SoC isn't b= eing woken >> up by FreeBSD. If I manually frob the EEBPCR register from the U-Boot p= rompt I see >> that the second core is booting U-Boot (after which things go bad obviou= sly). But >> from FreeBSD I don't seem to be able to get a kick. The only real diffe= rence I see >> between U-Boot and FreeBSD is that in FreeBSD we need to program the BPT= R register >> to have the boot page mapped to where the kernel is loaded. But I have n= o reason to >> suspect that this is in any way related to why I can't bring the 2nd cor= e up. >> BTW: The logic in FreeBSD worked fine on a P1020. >>=20 >> Does anyone know of any erratas I should be concerned about or have had = similar >> experiences they can share. >=20 > Hi Marcel, > I can confirm we noticed this problem on P2020DS not long ago with vanill= a SVN HEAD, however we haven't investigated this because our local changes = for the DPAA QorIQ (rebased against SVN HEAD from around the same time fram= e) seem to work fine on the P2020DS as well (SMP enabled). I'm still cleani= ng up and fractioning our huge diff for commiting to SVN and will test the = P2020 too. Ok, good. It's always good to get confirmation. It allows me to forget about firmware/load/kernel handoff and hardware. I'll let you know what I find out, once I solved the more urgent problem of /sbin/init not running at all (even on UP). Thanks, --=20 Marcel Moolenaar marcelm@juniper.net