Date: Sat, 8 Feb 2020 12:44:44 +0100 From: Michael Tuexen <tuexen@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org, Jeff Roberson <jeff@FreeBSD.org> Subject: Re: RPi3 not using SMP? Message-ID: <B009B338-F3EF-44A9-B562-7927FFE2D843@freebsd.org> In-Reply-To: <6B6CCB8F-B56A-4758-BEEC-6418718C95CB@yahoo.com> References: <20200208011940.GA8570@www.zefox.net> <6B6CCB8F-B56A-4758-BEEC-6418718C95CB@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 8. Feb 2020, at 03:46, Mark Millard via freebsd-arm = <freebsd-arm@freebsd.org> wrote: >=20 >=20 >=20 > On 2020-Feb-7, at 17:19, bob prohaska <fbsd at www.zefox.net> wrote: >=20 >> For some weeks now an RPi3 running -current has seemed rather = slow.... >>=20 >> On looking at the early part of the boot message the processor >> attributes seem rather scant: >>=20 >> ...... >> elease APs...APs not started >> CPU 0: ARM Cortex-A53 r0p4 affinity: 0 >> Instruction Set Attributes 0 =3D <CRC32> >> Instruction Set Attributes 1 =3D <> >> Processor Features 0 =3D <AdvSIMD,FP,EL3 32,EL2 32,EL1 32,EL0 = 32> >> Processor Features 1 =3D <> >> Memory Model Features 0 =3D <TGran4,TGran64,SNSMem,BigEnd,16bit = ASID,1TB PA> >> Memory Model Features 1 =3D <8bit VMID> >> Memory Model Features 2 =3D <32bit CCIDX,48bit VA> >> Debug Features 0 =3D <2 CTX BKPTs,4 Watchpoints,6 = Breakpoints,PMUv3,Debugv8> >> Debug Features 1 =3D <> >> Auxiliary Features 0 =3D <> >> Auxiliary Features 1 =3D <> >> CPU 1: (null) (null) r0p0 affinity: 0 >> CPU 2: (null) (null) r0p0 affinity: 0 >> CPU 3: (null) (null) r0p0 affinity: 0 >> ............ >> In a top window, STATE is reported as RUN, rather than the >> former CPUn. >>=20 >> Is a software switch now required to enable multiprocessing? >>=20 >> Or, could it be related to the lines: >> psci0: PSCI version number mismatched with DT=20 >> as pointed out by Mark M in reference to the cpu_reset failed >> problem, which is still manifest?=20 >>=20 >> The kernel is at r357644. >=20 > Head -r356767's kernel does not have this problem for RPi3/4 used as > aarch64 FreeBSD. >=20 > Head -r356776 and later all have this problem for both RPi3 and RPi4. >=20 > Note: There are no head versions between those. Did you ping Jeff (CCed), since it is his commit and he might know what = is going on? Best regards Michael >=20 > The console log shows evidence of the problem much earlier. > Instead of saying: >=20 > psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0 > psci0: PSCI version 0.2 compatible >=20 > (once) it says: >=20 > psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0 > psci0: PSCI version number 0 mismatched with DT, default 2 > device_attach: psci0 attach returned 6 >=20 > (and those 3 lines repeat in various places) for which none of > them show up for -r356767 . >=20 > Without identifying and using PSCI, the extra cores will not > start and the cpu(s) will not reset. (PSCI is the ARM interface > for doing such things.) >=20 > I've no clue why, but the version number it gets in my RPi4 > experiments is 0. My only guess is that at some point > memory important to ARM's PSCI operation has been touched > and is no longer valid for the PSCI operation. >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B009B338-F3EF-44A9-B562-7927FFE2D843>