Date: Wed, 14 Oct 2015 10:10:19 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 203765] Processes inside jail that use libthr get stuck in 'umtxn' state. 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203765-16-V8JP7gZ3XJ>