Date: Fri, 29 Nov 2024 16:19:03 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282994] Repeated kernel panics Message-ID: <bug-282994-227-ourctcGfbD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282994-227@https.bugs.freebsd.org/bugzilla/> References: <bug-282994-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282994 --- Comment #5 from Mark Johnston <markj@FreeBSD.org> --- > `all kinds of problems` sounds scary. Well, I just meant that without the patch, hitting the swapuse limit could cause a panic; with the patch, it'll cause shm_alloc() to fail. In the backtrace you pasted, the running process was php, so with the patch applie= d, either some php script or the runtime would have hit an error instead of triggering a panic. Maybe it can tolerate such errors just fine, but I don= 't know - that's all I meant by "all kinds of problems". > These happen randomly even when running as root with no rctl rules applie= d.=20 > - top takes thirty seconds to several minutes to load.=20 > - ps -aux takes several minutes to return results.=20 > - Nullfs mounts take several minutes to apply. Are you sure that no rctl rules are applied there? If you sent ctrl-T to the terminal while top/ps/mount are running, what gets printed? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282994-227-ourctcGfbD>