From owner-freebsd-arm@freebsd.org Sat Feb 8 21:38:43 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0C46624C58C for ; Sat, 8 Feb 2020 21:38:43 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic316-55.consmr.mail.gq1.yahoo.com (sonic316-55.consmr.mail.gq1.yahoo.com [98.137.69.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48FQXK5H95z4KpW for ; Sat, 8 Feb 2020 21:38:41 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: gWM7p_IVM1kPy0Em0IsNMxB55d_LSCezygBnP46btHvRuP7J.RPrSOVChdTaTbe tfGmmLUxaqakF9zjr4ecO0MGWd3emzIG3_NmFAkqopOFSpAKj2azdSw6J94kpkHkGTWTnWbz6twn VG6H1A4f19jE4t2_8zkl9ovW3XrWe753JL4AwRZmh1qxIGbiXYszqZpDMgCUqKRn9jfZDQ38hyUd jY3edEPBnwbjYTUjL.RLDRxPb6q5UOGAJ35tlKAK0aTrM1cJt71BoBlQ9WCGK3rZiCvqA31GE6C8 h8m_PB_3OAkT7DpwzNo9oascjocQoKQprVf8Psa9cifofhGAuJKzWsIuhcKv4.7CPq6esUMIsbxb .e10bjv95VaQE4tM8_OYoKw1imguDFWyIu449TLPNttmsm3I_o9xEGZHXAQ6zlGxkwhaVn5C3hjW F6m1F1rSq.up9kIHPpUisKDGzskPulLsFLM52JqgC9u4xaApRYm9rIYtZF4MjhjEkOHifIdjjCyj YRkBHQ7z9onTKjKBZ19O4JROZAi65bEafz0Ix4fdxk5w3HBD6HnYVctvfxuea6187J.mveQww6iF l7zm1g.EAI2nlhd._X36HljeAw3JXarQBXl9hdAjge9qY7d56hgvd6O6i9TIw6NajVNInYtnyjZa QyJQmLt9A41ffTh4tr_CfS7n7XRdCjwQbTfltzZ2zYQ4WUA9HxyKX2pf7QHOlI1ORZxuwrd3ZfZ3 olEIZzOCvOTAV6J2Cz9_m7u7Q0Psuy4WfwaRYbUiwYRVb1LL3auSDxI2TCzLo3HjI8g2po5j_5lb b1vDpT.U0VmZonMjmXq1o99LynMuRC1k4.w.oDtXBTG9IM7qWkpO4R3FfUZnovJ40DEvYWgki0UU MTOuOk9YZ3v.38nnCCijJ9cL.oHTJZh3QJdZZknr4QwwyZrtkAzrEYKrIprB3vAKKVE_FJoAD8Ga eP1PYwSOZacGXg_9On_ry9_vZEFmRhFbVq_l_hcHBAJRl9OKPMXFEGtsdv8qkSOGreJAtSvP3c3y WB257szFGLul4NmFgAQz6Dv3NNeTGTSOzXpFjzuuy8rdHFsT_x21pkfkwhJtnMRziliSFtY5y8VP nzIPj5110bU5GLBcGc3JUQNGt0XO56hW6ndJCpheWS1fx2BvCiTCRWqt3iKtVKjH5F432asCWrVw C7St0xN8jI2CvxLCF3Fm18QDTlScCN2hwM_o0WigQhQrTql6cIShQKoRd1ynFNNwrrmuwjJGagQg u44KAgiRCj2ChnSpaCWmOWPZO_DOEW2Ty2XUzbNxfjhDGhXK80NFc08WxUmV95XJqNl1f3UoHk5j QyU3kVxAUHWpASi.yLeet1IYY4mGApjCCGJE21KN576vtD8sepwFUbd9mx8DvPCTg.99MqD2xWtF fzFvDBgEJoEq4qj0eFOHEXokvaT0- Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Sat, 8 Feb 2020 21:38:39 +0000 Received: by smtp415.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID bfa4ee6a3da7c97a06195c238880151f; Sat, 08 Feb 2020 21:38:38 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) Subject: Re: RPi3 not using SMP? From: Mark Millard In-Reply-To: Date: Sat, 8 Feb 2020 13:38:37 -0800 Cc: bob prohaska , freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <643F7D8B-25CF-47FD-907F-820785A9E8D5@yahoo.com> References: <20200208011940.GA8570@www.zefox.net> <6B6CCB8F-B56A-4758-BEEC-6418718C95CB@yahoo.com> To: Michael Tuexen X-Mailer: Apple Mail (2.3608.60.0.2.5) X-Rspamd-Queue-Id: 48FQXK5H95z4KpW X-Spamd-Bar: / X-Spamd-Result: default: False [0.78 / 15.00]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.06)[-0.064,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (4.88), ipnet: 98.137.64.0/21(0.83), asn: 36647(0.66), country: US(-0.05)]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.34)[0.342,0]; RCVD_IN_DNSWL_NONE(0.00)[31.69.137.98.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Feb 2020 21:38:43 -0000 On 2020-Feb-8, at 03:44, Michael Tuexen wrote: >=20 >=20 >> On 8. Feb 2020, at 03:46, Mark Millard via freebsd-arm = wrote: >>=20 >>=20 >>=20 >> On 2020-Feb-7, at 17:19, bob prohaska 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 >>> Instruction Set Attributes 1 =3D <> >>> Processor Features 0 =3D >>> Processor Features 1 =3D <> >>> Memory Model Features 0 =3D >>> 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? My messages that contained additional evidence had jeff listed, including the one that you replied to. I've tended to remove Jeff from my messages that did not contain new evidence, including this message. I've not come up with any new ways to get potentially useful information. Other things than PSCI may be messed up. It is just the PSCI is the only thing with identified evidence and some known way to test for the problem being present vs. not. > Best regards > Michael >>=20 >> The console log shows evidence of the problem much earlier. >> Instead of saying: >>=20 >> psci0: on ofwbus0 >> psci0: PSCI version 0.2 compatible >>=20 >> (once) it says: >>=20 >> psci0: 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 >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)