Date: Fri, 12 Feb 2016 10:33:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 207085] pmc assertion failure: pmc %p non-NULL Message-ID: <bug-207085-8-LfpZULaC7G@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207085-8@https.bugs.freebsd.org/bugzilla/> References: <bug-207085-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=3D207085 Konstantin Belousov <kib@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #1 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to joss.upton from comment #0) So the question is how could pc_corepmcs[idx].phw_pmc become non-NULL legitimately there ? Context switch hooks should manage cpu slots, so I see= at least two possibilities: - cpu !=3D curcpu and something else context-switched on cpu which brought = its process-private pcms - global pcm was activated which took the slot. In fact, this is unlikely since sx lock is still owned. Could you look what pcm was in the slot for fired assert, and who is the ow= ner of it ? --=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-207085-8-LfpZULaC7G>