Date: Fri, 29 Nov 2024 16:11:10 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282994] Repeated kernel panics Message-ID: <bug-282994-227-QXqxssFSMe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282994-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=282994 --- Comment #4 from jSML4ThWwBID69YC@protonmail.com --- (In reply to Mark Johnston from comment #3) Thank you! There are rctl rules in place for every user account, exempting root and system services. Here's an example. # USERID < replace with actual uid. user:USERID:pcpu:deny=100/user user:USERID:maxproc:deny=50/user user:USERID:memoryuse:deny=1024MB/user user:USERID:swapuse:deny=1024MB/user user:USERID:readbps:throttle=200MB/user user:USERID:writebps:throttle=200MB/user Are the other symptoms also due to this? These happen randomly even when running as root with no rctl rules applied. - top takes thirty seconds to several minutes to load. - ps -aux takes several minutes to return results. - Nullfs mounts take several minutes to apply. The above issues started at the same time as the panics. All the affected systems are running 14.2-RC1. They were previously running 14.1-p6 with the same issue. My guess was it had something to do with FreeBSD-SA-24:14.umtx. > I wrote a patch which prevents the crash, but note that you'll get shm object allocation failures instead, which might cause all kinds of problems: https://reviews.freebsd.org/D47839 `all kinds of problems` sounds scary. I'm getting the impression that rctl is no longer safe to use, but what other options are there for resource control? Is it just the swapuse that's an issue? I'll try pulling the swap rules and see if it changes anything. -- 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-282994-227-QXqxssFSMe>