From nobody Sat Jul 29 23:55:53 2023 X-Original-To: freebsd-questions@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 4RD1bz02PQz4qGk1; Sat, 29 Jul 2023 23:55:59 +0000 (UTC) (envelope-from tom@khubla.com) Received: from mailout.easymail.ca (mailout.easymail.ca [64.68.200.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 4RD1by1WQZz3qrc; Sat, 29 Jul 2023 23:55:58 +0000 (UTC) (envelope-from tom@khubla.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of tom@khubla.com designates 64.68.200.34 as permitted sender) smtp.mailfrom=tom@khubla.com; dmarc=none Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id A670E60AE2; Sat, 29 Jul 2023 23:55:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at emo07-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo07-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RcHFhsu27RVs; Sat, 29 Jul 2023 23:55:55 +0000 (UTC) Received: from gargamel-2.ascot.khubla.lan (d198-166-24-90.abhsia.telus.net [198.166.24.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 97AC7615D0; Sat, 29 Jul 2023 23:55:55 +0000 (UTC) Subject: Re: FreeBSD 13.2-p1 hanging To: freebsd-questions@freebsd.org Cc: questions@freebsd.org References: <280960a2-6406-97bc-173b-0ddc7a2ce75a@khubla.com> <90c9f1e5-b1eb-3c54-2f37-fc35ae1570af@khubla.com> <48201e39-f3d1-488a-9d9a-7342ef91a54e@freebsd.org> <6fd724c5-1ac7-39a7-b805-91dcdcd73927@khubla.com> <5bdac425-adfd-2f98-c1ec-ecec6ea09508@freebsd.org> <5b220b92-8882-6755-f4a6-daedc11a4d30@Gmail.com> <5fdf71d3-fb0e-066a-d3ab-4963755afb08@khubla.com> <4000df51-8c93-0236-c62d-3ab4d460e028@freebsd.org> From: Tom Everett Message-ID: <77a99e88-3849-d645-5b2b-143cdca8a941@khubla.com> Date: Sat, 29 Jul 2023 17:55:53 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.60 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 In-Reply-To: <4000df51-8c93-0236-c62d-3ab4d460e028@freebsd.org> Content-Type: multipart/alternative; boundary="------------54766DDCCA7C1DB7B3CF135E" Content-Language: en-US X-Spamd-Result: default: False [-2.50 / 15.00]; URI_COUNT_ODD(1.00)[15]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; RCVD_IN_DNSWL_MED(-0.20)[64.68.200.34:from]; R_SPF_ALLOW(-0.20)[+ip4:64.68.200.0/22]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org,questions@freebsd.org]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:16686, ipnet:64.68.200.0/22, country:CA]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[khubla.com]; FREEFALL_USER(0.00)[tom]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4RD1by1WQZz3qrc X-Spamd-Bar: -- This is a multi-part message in MIME format. --------------54766DDCCA7C1DB7B3CF135E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Just an update on status.  I did three things: Disabled ASLR in /boot/loader.conf kern.elf64.aslr.enable=0 kern.elf32.aslr.enable=0 I did this b/c I read that in 13.2 it was automatically enabled. I also set a flag to control the growth of the ARC vfs.zfs.arc_max="4294967296" finally, since I have multiple jails, I wondered if something had changed that would make old userspace binaries a problem.  So I upgraded all jails with ezjail. The net result is that the host is up since about the 20th of the month. Thank everyone who took the time to respond to my ask for help. > Graham Perrin > July 15, 2023 at 9:49 AM > > On 13/07/2023 01:22, Tom Everett wrote: > > I should not treat freebsd-update as a sane approach to downgrading. > > Instead, if downgrade is essential, build from source. > > On the releng/13.2 branch > , tag release/13.2.0 > (preceding patch 1) is at: > > > commit aab15c8d11a299cc11fd1d1cd09aec11383c99bc > > > Tom Everett > July 12, 2023 at 6:22 PM > Well, it may be time to downgrade.  I've cleaned all the fans with > compressed air, since heat is always a suspect, and disconnected USB > devices.  Over the past two weeks the host now has an MTBF of about 2 > days.  Always the same symptom; it just freezes.   I enabled SMART on > the root disk; it seems to be healthy.  I don't see any concerning > messages in the logs. > > I am on FreeBSD 13.2-RELEASE-p1 GENERIC amd64 > > So, to downgrade to the previous kernel would this be the right > command-line? > > freebsd-update upgrade -r 13.2-RELEASE > freebsd-update install > freebsd-update install > pwd_mkdb /etc/master.passwd > pkg-static install -fy pkg > pkg upgrade -fy > freebsd-update install > reboot > > (instructions essentially from here: > https://lifeforms.nl/20141224/downgrading-with-freebsd-update) > > Graham Perrin > July 3, 2023 at 11:05 PM > > On 02/07/2023 00:50, Steven Friedrich wrote: > > Am I missing something? > > (This is a RELEASE case.) > > Steven Friedrich > July 1, 2023 at 5:50 PM > I would try the buildworld, buildkernel before spending time fretting. > YMMV. > > > > Graham Perrin > July 1, 2023 at 11:06 AM > On 01/07/2023 16:37, Tom Everett wrote: > > > > Add the line below to /etc/sysctl.conf then restart the OS. > > hw.acpi.power_button_state="S5" > > > S5 should cause a press on the power button to gracefully shut down > the computer. In my experience this button sometimes works when > FreeBSD is otherwise unresponsive. > > I guess, the next thing to consider would be graphics. > > -- Sent from Postbox --------------54766DDCCA7C1DB7B3CF135E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Just an update on status.  I did three things:

Disabled ASLR in /boot/loader.conf

kern.elf64.aslr.enable=0
kern.elf32.aslr.enable=0

I did this b/c I read that in 13.2 it was automatically enabled.

I also set a flag to control the growth of the ARC

vfs.zfs.arc_max="4294967296"

finally, since I have multiple jails, I wondered if something had changed that would make old userspace binaries a problem.  So I upgraded all jails with ezjail.

The net result is that the host is up since about the 20th of the month.

Thank everyone who took the time to respond to my ask for help.

July 15, 2023 at 9:49 AM

On 13/07/2023 01:22, Tom Everett wrote:

I should not treat freebsd-update as a sane approach to downgrading.

Instead, if downgrade is essential, build from source.

On the releng/13.2 branch <https://cgit.freebsd.org/src/log/?h=releng/13.2>, tag release/13.2.0 (preceding patch 1) is at:

<https://cgit.freebsd.org/src/tag/?h=release/13.2.0>
commit aab15c8d11a299cc11fd1d1cd09aec11383c99bc
<https://cgit.freebsd.org/src/commit/?id=aab15c8d11a299cc11fd1d1cd09aec11383c99bc>

July 12, 2023 at 6:22 PM
Well, it may be time to downgrade.  I've cleaned all the fans with compressed air, since heat is always a suspect, and disconnected USB devices.  Over the past two weeks the host now has an MTBF of about 2 days.  Always the same symptom; it just freezes.   I enabled SMART on the root disk; it seems to be healthy.  I don't see any concerning messages in the logs.

I am on FreeBSD 13.2-RELEASE-p1 GENERIC amd64

So, to downgrade to the previous kernel would this be the right command-line?

freebsd-update upgrade -r 13.2-RELEASE
freebsd-update install
freebsd-update install
pwd_mkdb /etc/master.passwd
pkg-static install -fy pkg
pkg upgrade -fy
freebsd-update install
reboot

(instructions essentially from here: https://lifeforms.nl/20141224/downgrading-with-freebsd-update)

July 3, 2023 at 11:05 PM

On 02/07/2023 00:50, Steven Friedrich wrote:

Am I missing something?

(This is a RELEASE case.)

July 1, 2023 at 5:50 PM
I would try the buildworld, buildkernel before spending time fretting. YMMV.



July 1, 2023 at 11:06 AM
On 01/07/2023 16:37, Tom Everett wrote:



Add the line below to /etc/sysctl.conf then restart the OS.

hw.acpi.power_button_state="S5"


S5 should cause a press on the power button to gracefully shut down the computer. In my experience this button sometimes works when FreeBSD is otherwise unresponsive.

I guess, the next thing to consider would be graphics.



--
Sent from Postbox
--------------54766DDCCA7C1DB7B3CF135E--