From owner-freebsd-amd64@freebsd.org  Fri Feb 12 10:33:15 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C00DAA6063
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Fri, 12 Feb 2016 10:33:15 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8B8EA1EC8
 for <freebsd-amd64@FreeBSD.org>; Fri, 12 Feb 2016 10:33:15 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1CAXEeS025742
 for <freebsd-amd64@FreeBSD.org>; Fri, 12 Feb 2016 10:33:15 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 207085] pmc assertion failure: pmc %p non-NULL
Date: Fri, 12 Feb 2016 10:33:15 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-207085-6-uVTZj7pM1V@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207085-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-207085-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 12 Feb 2016 12:06:11 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2016 10:33:15 -0000

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 on the CC list for the bug.=