From owner-freebsd-ppc@freebsd.org Thu Jan 31 01:18:53 2019 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41360133CF7B for ; Thu, 31 Jan 2019 01:18:53 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic316-14.consmr.mail.bf2.yahoo.com (sonic316-14.consmr.mail.bf2.yahoo.com [74.6.130.124]) (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 AD6E98D282 for ; Thu, 31 Jan 2019 01:18:51 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: gS8fO40VM1miTNzV4cnuR_X7Uqej.SJ9UnUCZb0nZj0XH12leScIX_SRFj9OPXm Waqo0RhCD_ia1qPDcbqCxMFGP70n6Lb18rdlw0c7NYb5nglioGfMM60GKwPRHtr3zDzgvG._gVGk fxHrTjZmJRQ7kN4vkXLX6yO61Z6kfYG7MF2hUb0eFRF_QeTnU4TE2_yog2vUmRLdZVALFAOaOCpr 8gIbKVi4bs4UpLU9PnjPCsGg_LcI66OjJJ5yb2w49B90ReN.wpjkKuvYXYhGYW7p3X.QG3J_GqmD .PiV8UDAfSrk2n8CtMCIVydGgK5gaYZvzSvNS30M02DbGIG6NLHDSsQFrD36soupQYO31M7Mikml 8JvXHrx0GchMWBK5sWOhHQaZUEjanw7C1rAHv88lEXRTWK3Fxs2av27jkbyYSjekIN04AkLdgy.U _sQLqQTydAueo.1NMua.3vaDgBLUgYlOHNqhO5DmcQ474UXCZ6o1Lt57OBhI6JRDlpC64INQ_esL 2NMS0PIFPftDTC8NnShbjlkvPkQTU8WiKv2Ddk1nvHo76HX5FrrTrTQOBn7yHnjQ3btPmLcAfUts ozLzJ3AxyYxq.N1LU2ZB.09P6HRrTZANAXx50Cd4kF6tYS9HHWESDLASkyOIjsriIyb_C84GLqYb wlgE_jrTSAwrRffKJPkvVTQ8tLqzHf_7haP0lZMe4JGTP.g5jgSY69MOJDMBN3guBXW1D49c3OiH ugATyppvYNPg08ig2h0APUHd4u6QG3Pyd1_.5e0WQ1F8tYUC4IIffGQs9aXrdhuKciwHHuty9kvY mcxC8.4i6Qy9bgFXhmyinUGvRV4pblKjpk2xPI2yqK0UbtFQkLgOoYvY.RVKacBGONjpk3w_Mhd2 35VEDtBEK9s1atJJpoZMa17fIeGRV2yeN69mFEL0wJ3xz_DElSvk64cTfPYfZgzpGTv3qFEkAW1X mwsJpo_SJaEXidddSnaCpNceg8tgnLOSjI_hmHpndWRrld91Fzz.5WBsweX50lPIL2HhrfNEAXpo yrQTrrT4QYcYnpCv0tyNRvmSKUuhngXNHJ03TAjcj0kCi90XXqjxaB_E- Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.bf2.yahoo.com with HTTP; Thu, 31 Jan 2019 01:18:50 +0000 Received: from c-67-170-167-181.hsd1.or.comcast.net (EHLO [192.168.1.113]) ([67.170.167.181]) by smtp424.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID c437f2be11c133cb22b9eae88c2cd8a0 for ; Thu, 31 Jan 2019 01:18:47 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: PoerMac G5 "4 core" (system total): some from-power-off booting observations of the modern VM_MAX_KERNEL_ADDRESS value mixed with usefdt=1 Date: Wed, 30 Jan 2019 17:18:45 -0800 References: <2153561F-FE12-4BA0-9856-F75110401AB6@yahoo.com> To: FreeBSD PowerPC ML In-Reply-To: <2153561F-FE12-4BA0-9856-F75110401AB6@yahoo.com> Message-Id: X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: AD6E98D282 X-Spamd-Bar: +++ X-Spamd-Result: default: False [3.26 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MV_CASE(0.50)[]; FREEMAIL_FROM(0.00)[yahoo.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; MX_GOOD(-0.01)[cached: mta6.am0.yahoodns.net]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:26101, ipnet:74.6.128.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)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.99)[0.994,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ppc@freebsd.org]; NEURAL_SPAM_MEDIUM(0.79)[0.791,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(1.11)[ip: (3.09), ipnet: 74.6.128.0/21(1.42), asn: 26101(1.13), country: US(-0.07)]; NEURAL_SPAM_LONG(0.87)[0.875,0]; RCVD_IN_DNSWL_NONE(0.00)[124.130.6.74.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2019 01:18:53 -0000 [Where boot -v output is different between booting to completion vs. hanging up: actual text.] On 2019-Jan-29, at 17:52, Mark Millard wrote: > For the modern VM_MAX_KERNEL_ADDRESS value and also use of the = usefdt=3D1 case: >=20 > This usually hang during boot during the "Waking up CPU" message = sequence. >=20 > But not always. Powering off and retrying , sometimes just a few = times, and > other times dozens of times, the system that I have access to does = eventually > boot for the combination. So some sort of race condition or lack of = stable > initialization? >=20 > When it does boot, smp seems to be set up and working. >=20 > Once booted, it is usually not very long until the fans are going = wild, > other than an occasional, temporary lull. >=20 >=20 >=20 > For for shutting down the following applies to both = VM_MAX_KERNEL_ADDRESS > values when a usefdt=3D1 type of context is in use: >=20 > When I've kept explicit track, I've not had any example of all of the: >=20 > Waiting (max 60 seconds) for system thread `bufdaemon' to stop... > Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to = stop... > Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to = stop... > . . . >=20 > getting to "done": instead one or more time out. Which and how many > vary. >=20 > The fans tend to take off for both VM_MAX_KERNEL_ADDRESS values. The > buf*daemon timeouts happen even if the fans have not taken off. >=20 With VM_MAX_KERNEL_ADDRESS reverted or a successful boot with the modern value: Adding CPU 0, hwref=3Dcd38, awake=3D1 Waking up CPU 3 (dev=3Dc480) Adding CPU 3, hwref=3Dc480, awake=3D1 Waking up CPU 2 (dev=3Dc768) Adding CPU 2, hwref=3Dc768, awake=3D1 Waking up CPU 1 (dev=3Dca50) Adding CPU 1, hwref=3Dca50, awake=3D1 SMP: AP CPU #3 launched SMP: AP CPU #2 launched SMP: AP CPU #1 launched Trying to mount root from ufs:/dev/ufs/FBSDG5L2rootfs [rw,noatime]... With the modern VM_MAX_KERNEL_ADDRESS value for a boot attempt that failed, an example (typed from a picture of the screen) is: Adding CPU 0, hwref=3Dcd38, awake=3D1 Waking up CPU 3 (dev=3Dc480) Another is: Adding CPU 0, hwref=3Dcd38, awake=3D1 Waking up CPU 3 (dev=3Dc480) Waking up CPU 2 (dev=3Dc768) (Both examples have no more output.) So CPUs 1..3 do not get "Adding CPU" messages. Also: I do not remember seeing all 3 "Waking up CPU" messages, just 1 or 2 of them. (Sometimes the "Trying to mount root from" message is in the mix as I remember.) One point of difference that is consistently observable for the old vs. modern VM_MAX_KERNEL_ADDRESS values is how many bufspacedaemon-* threads there are: old VM_MAX_KERNEL_ADDRESS value: 0..2 new VM_MAX_KERNEL_ADDRESS value: 0..6 I have had many boot attempts in a row boot for the modern VM_MAX_KERNEL_ADDRESS value, though not as many as the dozens of failures in a row. Highly variable with lots of testing. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)