Date: Fri, 22 Aug 2025 20:40:48 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 288777] System freezes after upgrading to 14.3-RELEASE Message-ID: <bug-288777-227-PBb3eAWMW8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-288777-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288777 --- Comment #10 from Bren <BlueSkiesApplePies+FreeBUG@pm.me> --- Good to know. I don't see any evidence whatsoever that a dump is even being attempted which lead me to believe that maybe I didn't have enough space. # dumpon -l mirror/swap Coincidentally, as soon as I read this, the server seized up again. I was running: # freebsd-version -kru 14.2-RELEASE-p1 14.2-RELEASE-p1 14.2-RELEASE-p5 We've been using rsync to sync snapdirs for years and have never seen an issue like this (we are rsync'ing the the live filesystem now hoping that would help). Rebooted into 14.3. Dumps are definitely configured. Triggered a panic manually and the system said I needed about 4.2GB but only have 2GB. Turned on compression which seemed to allow the dump to complete, but there is still no dump file in /var/crash. Now that I write this, I wonder if it's because I'm using mirrored encrypted swap that is wiped on every boot. Logs say the dump will be written unencrypted, but I think it's getting wiped either way. Will need to reconfigure this. Still trying to figure out the correct parameters to get watchdogd working correctly. Before, when I was rsync'ing the snapdirs, just running a simple '/bin/ps' would be enough trigger watchdog when the system would freeze. That doesn't work now, so I made a script that touches a few files. Hopefully I can get a proper dump soon. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-288777-227-PBb3eAWMW8>