From owner-freebsd-threads@freebsd.org  Wed Nov 11 16:34:00 2015
Return-Path: <owner-freebsd-threads@freebsd.org>
Delivered-To: freebsd-threads@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 43D32A2C375
 for <freebsd-threads@mailman.ysv.freebsd.org>;
 Wed, 11 Nov 2015 16:34:00 +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 2FF1E1538
 for <freebsd-threads@FreeBSD.org>; Wed, 11 Nov 2015 16:34:00 +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 tABGY0uH055887
 for <freebsd-threads@FreeBSD.org>; Wed, 11 Nov 2015 16:34:00 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 200992] proccess won't die in thread_suspend_switch
Date: Wed, 11 Nov 2015 16:33:59 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: threads
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: swills@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200992-16-gwzXgOFJcR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200992-16@https.bugs.freebsd.org/bugzilla/>
References: <bug-200992-16@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads/>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Nov 2015 16:34:00 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200992

--- Comment #17 from Steve Wills <swills@FreeBSD.org> ---
(In reply to johans from comment #15)
The delay may be partially my fault, as I hadn't responded to the request for
feedback regarding the patch solving my original issue. I hadn't experienced
the issue very frequently (not nearly as frequently as you) so even though I
had been running my system with the patch for a while, I wasn't confident it
had been resolved. That said, it has been a while now and I haven't seen the
issue. Given how it has solved the issue for you as well, we should definitely
look at getting it committed and merged, and perhaps an errata issued.

-- 
You are receiving this mail because:
You are the assignee for the bug.