From nobody Sat Sep 23 19:41:34 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RtKJx6V3Pz4v8DL for ; Sat, 23 Sep 2023 19:41:53 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic313-20.consmr.mail.gq1.yahoo.com (sonic313-20.consmr.mail.gq1.yahoo.com [98.137.65.83]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RtKJx2hQXz3H6l for ; Sat, 23 Sep 2023 19:41:53 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1695498110; bh=/hf3lKPUy8kY1L1uSF6K1RMtjQyrEQVNj41VkVsoe20=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=Xgx9u+bs+4NsC0wNiEGDcQvIIi1/P4uJTrdyvLS92qRmRjR4rfQ2/r6udUytiXOs3EYWGoffdfTavynqSxCG+Qc2Br/PaRAIjw2nJbE80KE9qMCdUs+l/ehua33L6hdWXWb47k3HqLk+gLgtQlMiDdWqf24eJByZ1VDv3rpxzIgoWgNOUiKb2yljm+BQSkMSIRn6bK5Qu0i2FhBZFLlq1kk/MuOWGs8jNqH/HQo8mXy+3j4imPZi6aIZgK+R880gv7zWyi72m7JJv/3eEkrGaNW752oGwC314d2CUMVnQgdsHtRq54N2a+/bx6EJtL5LxlRt19JveEAm4uaWWjlBMg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1695498110; bh=w+rnL4zKLfRXJ4hJTRzeugY1lk3e+pEulHZ0Tb4hKyd=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=rzhr9aRqmPJ2WhSbrjljLttvci0NRgnssZ3rD5TmqB8D6E76oX9zi601PMeQqWZC4knGyh35/ZixBRatQYjLwU53lAUM94qX+SOcMxA45AJHc/mgJW339nsLvFPzhRBWUV20ulK3phxGoUTOeE0hep4rZI4dnbqQz/DsjfWr713o74xohL/LaY/1xxRmlL6PJr0lF1UHomDGVhVAW7C6opjxwzp5girQKPcKLfV+SW18YOXhmXPhl7bozrP8chyABu/vqFJf7VjCl9M8cT18rieqWWtAt1JAycoeDKtsuzpO1GpAFg4cp5oJK3LrxfYTcfTU+f+CR/HaaPkQsgqEfw== X-YMail-OSG: Cy68zjgVM1k4QEQ2GKVjRpipUBeArmNHw7dK3VXFr1NClb5_LgqjyRgXBci5ujY 9WmS8HFbb5qrb.cSSgxksJwZi.4Ll1KwKteFxLiXlGXF65PGbSAV9uBHw4WTfx2r3hok27ulaOe0 L7Z_M4fRM.9B3Je1OaXwh_PveapW4txKs8Ws2Eu2wkyYSo4IDlBQIVomFEMPpkuB5eGCyvZYCLcd v8d71mvPSfx2B4MDwShJHmtKfz4UGy4hO6zTK9iqwSnWnWn2U_vBK7kyFRu76iix_cWHhfQ4GNv2 BTc4EAq87OBH4raL0PIOJDizElLcet4gyDGAOjAc2in.mS1RhKKNN22fCiWupG_vf2iFPg3CDmC7 9PHDaB4Cdgf4KYWyGaAHLXNid4LouwQq_bKPCdul753koQNVLo9qxKxqRp7BgbOxge35V.hHdAdH jjmzAKq_g2GgIYEclIEF5OWAnkEpwxqTrCWqseMfEbQr72YJOlPeY.qCoXI_k9QjN.BpDdZILh_v GhK.XS7ONdwpFOqBLJKBe.aYH3V4_u6oz5GT_zvfqZv9Y0v24MU1TDK2CQtWxdp7VMBcRXKdDPKD Foq4RDv494c0DnbFhCdRbbyB3kMzFZz9Rx5xKssYHKRzdHhq5ioUilO1ufT4ClLR1J6sIu.qNfut EKJH2pIcVwLy_NOU6jNSeme2lj.w.uNvh1sFKdm_fTr_rrPKndL0_upCURN5aj6VHJEYr7FITLzV W5pKXXSZILPPUv1hcBlJChO5k.3GbS5Z8yMCAzkjW5yxFyFIyniV7hq4wP5Gbxkt7pwcgVdd6Mvm XB7nmz36qbmer4JQ96v_cnh4jzb9qnXU52dMH0Ol7JBcjOf_J5Z8nEd8VWIR_5A6UmTqgKW5bvkM r7FEPl8cvtTG9VNqZpVlEvP0FjgXcJlRD4uvHGULNDiZ9dx_PqQWYWJio2jOXIFMzWJEtQgk.hVk oySh8NCJugeZkelMcwfdPdBTbx1zikh5jaY3KbGLPSCcOP.sVdY4iOrmUGZN7mg7.eitpcspmeya t9L_7kdFZJTVKw4Mj6htVpSrCC.3t1oQgAi5k2boHQZx83rc3m2u6LX.ABjy5FdddVz.Dhygatxn 26CQKEQ17zoZI4nmNSgN9sU2jjO40qL3JbbAfO9u6ZUpVy.yLCBMIX6EWm4WjlVaVQKy5VdrIDLb nx7tv8t97MgP8F1EWWmt7tYW030fpPpCWF43qPkD6SQSg3UjhuhmeMqvTgpKLYlew2eZ0FPrMecJ Dxp7CkyeOYErNu3wQ25v84pjgAm00kdnzPrixdK4L7qFu6_7sTDGb5GBBIUwO0Va9iJfky0SfhJW NaciNraONHO.Is8mENhunfY9ETVSdg.ugQecehcwjJ4d7TgNjsrIJ7lQ4JQQPMTgDRDrZG_S6IUh o_3cjFFTiNsE3uQI_PNzvUo44PybLYws2sjABimGLOdEgsNpkietr93nsEdjUvJhGR.eedB5e2.u sRRgABdVJohVvzD.EF9kiNkKdTxgIgh11GvolaKzE5JsQ7EDRnMF_oE7mv0SQK5F0fPfdRa4CUoe anZq_szOzHSYqoPcLkxdRfiYc2.cMAWH1usfaST448wONrskAhuXfDCqAXCjVeVVRxWCoHmbGyTY DpHgxPBSt0vgP5gVw0Nmjjjriv_rRBAXw1xQf3YR4dx63GiNAT.2UOWyC_jGZU2gLxH1qTmCvwHE zIbCiITU57GXnQe86f.2h_q.Q9UI2FhoUdR0cgnXcEo_j_odBuGFoaxyWeUYkLLhRpfAnidb0slC m4FfeQVv2QEyAXOp85DqDY11Jmslc196IVCRSuZ6UXW3ZjCV_GmCwXyXk6enNQjH2jd71IPTH.8X 3NEqxu5WrcgJ6vvtc45He__aMk3nwRAMlwS8J8FRJgViNJ2w9umYyjDfHkNhfjsfs1osU5p8rxNr _GchRL0xyiuE0w2vWcQHebBoXXPXjk037iJlnONKh1HNXQ1me.b8kfHHKT5H9qgsnEyAg19Rkx77 fW0IlQC7aceKCk0GOo2cydDaAwtJaaN8jW1ZkiNMr6hVPaGnJ8LOstuJj194vP3yZSKZzWD7Fg7r UHp_BgrDQu6MMvooggi1FUY_U5ifpRA9vaUt78Ll6YJLTULXktql0DA4sz9r2yuiZheYw4kASpjT R0v3D0AqBTVuoBhr_SszXddQr1JfpW6ugi4Dq1q74xNnMuPizUOpDClRZnX5l8pNn.gYuCq_Sz4i S8oo96Avuu1.cgVvmCuRyjeOZCVNf6dCMACsvmQH7UHMiXOBp6TGy0qIVOOR29XWUTkmkryFbwy1 0ag-- X-Sonic-MF: X-Sonic-ID: e2213974-7510-43c9-a22a-9b2f64a9006b Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Sat, 23 Sep 2023 19:41:50 +0000 Received: by hermes--production-ne1-6cbd549489-2lmpf (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID f4d1ea7c5ae52de2ef27dc0b9a500d46; Sat, 23 Sep 2023 19:41:45 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\)) Subject: Re: Shutdown -r under -current hangs on RPi3 From: Mark Millard In-Reply-To: Date: Sat, 23 Sep 2023 12:41:34 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <0AADDACB-ABA3-47FF-B3A7-05B313F5326C@yahoo.com> <9D29DD48-1572-4C04-AD88-8436AC8DDDCC@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3731.700.6) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Queue-Id: 4RtKJx2hQXz3H6l On Sep 23, 2023, at 12:16, bob prohaska wrote: > On Sat, Sep 23, 2023 at 11:34:41AM -0700, Mark Millard wrote: >> On Sep 23, 2023, at 11:26, Mark Millard wrote: >>=20 >>> On Sep 23, 2023, at 08:52, bob prohaska wrote: >>>=20 >>>> =46rom time to time, but seemingly more often lately, a Pi3 >>>> get stuck during shutdown -r. The machine is running -current >>>> from a mechanical usb hard disk through a powered hub. No micro >>>> SD card is used. Once up it's quite stable. >>>>=20 >>>> The console reports >>>>=20 >>>> login: Sep 23 08:20:37 pelorus shutdown[224]: reboot by bob: >>>> Stopping sshd. >>>> Waiting for PIDS: 1063. >>>> Stopping cron. >>>> Waiting for PIDS: 1073. >>>> Stopping powerd. >>>> Waiting for PIDS: 1002. >>>> Stopping devd. >>>> Waiting for PIDS: 752. >>>> Writing entropy file: . >>>> Writing early boot entropy file: . >>>> . >>>> Terminated >>>> Sep 23 08:20:43 pelorus syslogd: exiting on signal 15 >>>> Waiting (max 60 seconds) for system process `vnlru' to stop... done >>>>=20 >>>> Waiting (max 60 seconds) for system process `syncer' to stop... = Syncing disks, vnodes remaining... 4 0 0 0 done >>>> All buffers synced. >>>> Uptime: 23h31m45s >>>> Khelp module "ertt" can't unload until its refcount drops from 1 to = 0. >>>=20 >>> I've gotten the above message on rare occasions over the years on >>> the amd64 system (ThreadRipper 1950X). (But reboots and shutdowns >>> are not frequent for this system normally.) >>>=20 >>> There is a recent: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271677 >>>=20 >>> It is not just your context with the issue. >>>=20 >>>> Resetting system ... >>>>=20 >>>> At that point all activity ceases. The only clue I can recognize is = that >>>> the red power LED remains off, as if FreeBSD never relinquishes = control >>>> to the Pi firmware, which turns the LED back on at powerup. = Power-cycling >>>> results in a normal reboot. >>>=20 >>=20 >> The system might produce more messages about the >> shutdown activity if it has been booted via: >>=20 >> boot -v >>=20 >> This might narrow down the context some for someone >> familiar with the messages --if oyu are lucky enough >> to eventually get an example from a boot -v context. >=20 > I'm confused here. Boot is normal, and it doesn't > seem to even reach the boot stage during reboot. Can > boot -v affect the _next_ boot? boot -v can add messages both to boot-time and to the later reboot/shutdown-time. You would have to keep booting with "boot -v", hoping that the later reboot/shutdown would report extra messages but would also include the 'help module "ertt" can't unload' message in the sequence. Once you had such a boot, you would report the text around the 'help module "ertt" can't unload' message to show the extra context. > It isn't clear to me that the bug report is related. It > seems to focus on the ertt message, while my problems > wait until the system claims to be resetting and then > gets stuck. I've had to force poweroff after some of the messages. The "can't unload until its refcount drops from 1 to 0" suggests that it is waiting to unload. (But I've no low level detail establishing that is actually what was going on.) Have you recently had it get stuck without first having the 'Khelp module "ertt" can't unload' message? (I've not had other reboot hangups except for other known problems that were later fixed. I've not had other reboot/shutdown hangups in a very long time.) > Maybe the ertt error is related, but the > association isn't consistent=20 Are you saying that in recent times you have had hangups that did not first show the 'Khelp module "ertt" can't unload' message? The message suggests that the refcount decreasing would lead to it not waiting any longer. (But I've no low level detail establishing that is actually what was going on when I did not have to force power off.) > Unfortunately the hang does not seem easily reproducible. Consistent with my "rare". > Several consecutive shutdown -r reboots were successful. To my knowledge/memory, I've never gotten the message after being booted for only a short time (little activity). > The hangs seen so far have all followed OS build/install > sessions. So a "boot -v" before such sessions might, eventually, prove useful. =3D=3D=3D Mark Millard marklmi at yahoo.com