Date: Thu, 29 Mar 2018 14:35:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 227041] Kernel cannot fork new process after calling pmc_deatch with pid 0 Message-ID: <bug-227041-8-xYr6J9kfIF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227041-8@https.bugs.freebsd.org/bugzilla/> References: <bug-227041-8@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=3D227041 --- Comment #3 from Dom <dom@itsallbroken.com> --- Hi Conrad, thanks for the quick reply. I can't see any LORs when reproducing this issue and I can't seem to dtrace= my way to a culprit either. If pmc_release() is called the system livelocks immediately every time, how= ever if it's left out the first run of pmc-crash does not crash, and the second = run will either force an immediate reboot (again with nothing in the console) or run successfully, but attempting to unload hwpmc livelocks. If pmc-crash successfully exits subsequent runs pmc_allocate() returns EINVAL. At least one pmc_read() must be performed for either of these livelocks to occur. After either, pressing the power button starts to cleanly power off = but deadlocks after geli detaches my encrypted swap. I've also discovered two almost definitely unrelated LORs: - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227065 - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196799 --=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-227041-8-xYr6J9kfIF>