Date: Mon, 18 Nov 2024 16:03:58 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282713] Process enters in STOP state and doesn't respond to any signal. Message-ID: <bug-282713-227-A0ahYJnS9z@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282713-227@https.bugs.freebsd.org/bugzilla/> References: <bug-282713-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=3D282713 --- Comment #8 from Rupesh Pilania <rupeshpilania@gmail.com> --- (In reply to Rupesh Pilania from comment #7) Looks like there are no process sharing locking mechanism was used. I suspe= ct somehow kern.ipc.umtx_max_robust count can impact something. As per libthr = it's default value is 1000. So created 1 process with 1000 robust mutexes and ra= n 2 instances of this. Looks like somehow it slowed down other process. Now tho= se processes are unkillable. But I am not seeing processes waiting in umtxqb.= =20 Using 8 CPUs 16 GB RAM Somehow process with 1000 threads with robust mutexes impacted other proces= ses. Also saw this in one of the other process which went in stop state. ./procstat -k 917 PID TID COMM TDNAME KSTACK 917 100288 process1 - mi_switch thread_suspend_switch ptracestop cursig ast doreti_ast Similar to this https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200992 --=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-282713-227-A0ahYJnS9z>