From owner-freebsd-threads@freebsd.org  Wed Oct 14 10:10:19 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 6D6F5A11F42
 for <freebsd-threads@mailman.ysv.freebsd.org>;
 Wed, 14 Oct 2015 10:10:19 +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 5A54D10A8
 for <freebsd-threads@FreeBSD.org>; Wed, 14 Oct 2015 10:10:19 +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 t9EAAJvD017314
 for <freebsd-threads@FreeBSD.org>; Wed, 14 Oct 2015 10:10:19 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 203765] Processes inside jail that use libthr get stuck in
 'umtxn' state.
Date: Wed, 14 Oct 2015 10:10:19 +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: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: kib@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: cc
Message-ID: <bug-203765-16-V8JP7gZ3XJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203765-16@https.bugs.freebsd.org/bugzilla/>
References: <bug-203765-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, 14 Oct 2015 10:10:19 -0000

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

Konstantin Belousov <kib@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kib@FreeBSD.org

--- Comment #2 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Emiel Kollof from comment #0)
I cannot reproduce this on stable/10:

pooma% stty tostop
pooma% ./pr203765&
[1] 62024
pooma%
[1]  + 62024 suspended (tty output)  ./pr203765
pooma% fg
[1]  + 62024 continued  ./pr203765
Thread 1 message Thread 1 
Thread 2 message Thread 2 
pooma% jobs
pooma%

Same when I tried the same sequence jailed.

First question, can you reproduce the behavior on the host ?  If no, compare
the libc and libthr on the host and in the jail.

Second question, if the behavior is reproducable on host, try, at least
temporary, installing stable/10 kernel without touching the userland, and see
if the issue is still there

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