From owner-freebsd-threads@freebsd.org  Wed Nov 11 14:50:12 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 E9118A2B5F1
 for <freebsd-threads@mailman.ysv.freebsd.org>;
 Wed, 11 Nov 2015 14:50:12 +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 CDE261AE1
 for <freebsd-threads@FreeBSD.org>; Wed, 11 Nov 2015 14:50:12 +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 tABEoC9i038871
 for <freebsd-threads@FreeBSD.org>; Wed, 11 Nov 2015 14:50:12 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 14:50:12 +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: johan@300.nl
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: cc
Message-ID: <bug-200992-16-zkfxg3hnnk@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 14:50:13 -0000

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

johans <johan@300.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johan@300.nl

--- Comment #15 from johans <johan@300.nl> ---
I've been seeing almost identical problems on 10.2-RELEASE machines which run
under KVM virtualisation. I've had to reboot roughly 2 machines per day as a
workaround due to processes like Apache, HAProxy and Postfix getting stuck and
blocking any new instances starting up due to the listening sockets getting
trapped with the stuck processes.

Applying the patch of this PR fixed all our problems.

Are there any concrete reasons / problems to not go forward with this patch? If
not, I would like to suggest to get this committed with MFC to stable/10 and
nominate this for an errata. This problem makes running 10.2-RELEASE highly
problematic in virtualised environments with a decent workload.

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