From owner-freebsd-threads@freebsd.org Mon Mar 14 10:37:41 2016 Return-Path: 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 1B085ACF16F for ; Mon, 14 Mar 2016 10:37:41 +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 0C79E1882 for ; Mon, 14 Mar 2016 10:37:41 +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 u2EAbeOZ062473 for ; Mon, 14 Mar 2016 10:37:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Mon, 14 Mar 2016 10:37:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 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-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 10:37:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #64 from Konstantin Belousov --- (In reply to Robert Blayzor from comment #63) Sorry for delay with replying. For debugging purposes, please set debug.vn_io_fault_enable to 0, this should stop the message flood. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Tue Mar 15 10:46:01 2016 Return-Path: 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 56849ACF325 for ; Tue, 15 Mar 2016 10:46:01 +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 48C04264 for ; Tue, 15 Mar 2016 10:46:01 +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 u2FAjxD4024715 for ; Tue, 15 Mar 2016 10:46:01 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: Tue, 15 Mar 2016 10:46:00 +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: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2016 10:46:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200992 --- Comment #29 from commit-hook@freebsd.org --- A commit references this bug: Author: kib Date: Tue Mar 15 10:45:56 UTC 2016 New revision: 296896 URL: https://svnweb.freebsd.org/changeset/base/296896 Log: MFC r296320: Adjust _callout_stop_safe() return value for the subr_sleepqueue.c needs when migrating callout was blocked, but running one was not. PR: 200992 Changes: _U stable/10/ stable/10/sys/kern/kern_timeout.c stable/10/sys/kern/subr_sleepqueue.c stable/10/sys/sys/callout.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Tue Mar 15 17:10:15 2016 Return-Path: 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 28719AD1DAD for ; Tue, 15 Mar 2016 17:10: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 168261F12 for ; Tue, 15 Mar 2016 17:10: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 u2FHACWa031373 for ; Tue, 15 Mar 2016 17:10:14 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: Tue, 15 Mar 2016 17:10:13 +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: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2016 17:10:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200992 --- Comment #30 from commit-hook@freebsd.org --- A commit references this bug: Author: kib Date: Tue Mar 15 17:09:28 UTC 2016 New revision: 296913 URL: https://svnweb.freebsd.org/changeset/base/296913 Log: MFC r296320: Adjust _callout_stop_safe() return value for the subr_sleepqueue.c needs when migrating callout was blocked, but running one was not. PR: 200992 Approved by: re (marius) Changes: _U releng/10.3/ releng/10.3/sys/kern/kern_timeout.c releng/10.3/sys/kern/subr_sleepqueue.c releng/10.3/sys/sys/callout.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Fri Mar 18 12:03:42 2016 Return-Path: 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 B50DEAD5167 for ; Fri, 18 Mar 2016 12:03:42 +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 A48291E9E for ; Fri, 18 Mar 2016 12:03:42 +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 u2IC3g30061247 for ; Fri, 18 Mar 2016 12:03:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Fri, 18 Mar 2016 12:03:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rblayzor@inoc.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 12:03:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #65 from Robert Blayzor --- Here was a recent crash... Mar 15 11:58:17.019 mta1.alb kernel: pid 69942 kpf 2 Mar 15 11:58:17.019 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.019 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.019 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.019 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.019 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.019 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.019 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.019 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.221 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.425 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.625 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.626 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.626 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.626 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.626 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.833 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:17.834 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.034 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.034 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.034 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.034 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.034 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.034 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.034 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.035 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.238 mta1.alb kernel: pid 69942 kpf 1 Mar 15 11:58:18.238 mta1.alb kernel: <6>pid 69942 (exim), uid 26: exited on signal 11 (core dumped) procstat -v exim.core Password: PID START END PRT RES PRES REF SHD FL TP P= ATH 69942 0x400000 0x560000 r-x 314 325 3 1 CN-- vn /usr/local/sbin/exim 69942 0x760000 0x76a000 rw- 10 0 2 1 CN-- vn /usr/local/sbin/exim 69942 0x76a000 0x779000 rw- 5 5 2 1 CN-- df 69942 0x800760000 0x80077e000 r-x 30 30 33 0 CN-- vn /libexec/ld-elf.so.1 69942 0x80077e000 0x800785000 rw- 7 7 2 0 CN-- df 69942 0x800787000 0x8007b7000 rw- 40 40 2 1 CN-- df 69942 0x80097d000 0x80097f000 rw- 2 2 2 0 CN-- df 69942 0x80097f000 0x80098d000 r-x 14 15 7 3 CN-- vn 69942 0x80098d000 0x800b8d000 --- 0 0 2 0 CN-- df 69942 0x800b8d000 0x800b8e000 rw- 1 0 2 0 CN-- vn 69942 0x800b8e000 0x800b9f000 rw- 0 0 0 0 ---- -- 69942 0x800b9f000 0x800bc8000 r-x 41 41 9 4 CN-- vn 69942 0x800bc8000 0x800dc7000 --- 0 0 2 0 CN-- df 69942 0x800dc7000 0x800dc8000 rw- 1 0 2 0 CN-- vn 69942 0x800dc8000 0x800dd8000 r-x 16 17 19 9 CN-- vn 69942 0x800dd8000 0x800fd8000 --- 0 0 2 0 CN-- df 69942 0x800fd8000 0x800fd9000 rw- 1 0 2 0 CN-- vn 69942 0x800fd9000 0x800fdb000 rw- 0 0 0 0 ---- -- 69942 0x800fdb000 0x800ff3000 r-x 18 20 3 1 CN-- vn 69942 0x800ff3000 0x8011f3000 --- 0 0 2 0 CN-- df 69942 0x8011f3000 0x8011f5000 rw- 2 0 2 0 CN-- vn 69942 0x8011f5000 0x80120d000 r-x 24 25 18 8 CN-- vn 69942 0x80120d000 0x80140d000 --- 0 0 2 0 CN-- df 69942 0x80140d000 0x80140e000 rw- 1 0 2 0 CN-- vn 69942 0x80140e000 0x80141a000 rw- 12 0 1 0 C--- df 69942 0x80141a000 0x801445000 r-x 38 41 5 2 CN-- vn 69942 0x801445000 0x801645000 --- 0 0 2 0 CN-- df 69942 0x801645000 0x801648000 rw- 3 0 2 0 CN-- vn 69942 0x801648000 0x80181d000 r-x 404 412 3 1 CN-- vn /usr/local/lib/perl5/5.22/mach/CORE/libperl.so.5.22.1 69942 0x80181d000 0x801a1c000 --- 0 0 2 0 CN-- df 69942 0x801a1c000 0x801a25000 rw- 9 0 2 0 CN-- vn /usr/local/lib/perl5/5.22/mach/CORE/libperl.so.5.22.1 69942 0x801a25000 0x801a88000 r-x 84 94 27 13 CN-- vn /usr/lib/libssl.so.7 69942 0x801a88000 0x801c88000 --- 0 0 2 0 CN-- df 69942 0x801c88000 0x801c92000 rw- 10 0 2 0 CN-- vn /usr/lib/libssl.so.7 69942 0x801c92000 0x801e5f000 r-x 461 501 31 15 CN-- vn /lib/libcrypto.so.7 69942 0x801e5f000 0x80205f000 --- 0 0 2 0 CN-- df 69942 0x80205f000 0x802087000 rw- 40 0 2 0 CN-- vn /lib/libcrypto.so.7 69942 0x802087000 0x802089000 rw- 1 1 2 0 CN-- df 69942 0x802089000 0x8020fe000 r-x 45 45 8 3 CN-- vn 69942 0x8020fe000 0x8022fd000 --- 0 0 2 0 CN-- df 69942 0x8022fd000 0x8022fe000 rw- 1 0 2 0 CN-- vn 69942 0x8022fe000 0x802476000 r-x 376 387 64 31 CN-- vn /lib/libc.so.7 69942 0x802476000 0x802675000 --- 0 0 2 0 CN-- df 69942 0x802675000 0x802681000 rw- 12 0 2 0 CN-- vn /lib/libc.so.7 69942 0x802681000 0x8026ab000 rw- 11 11 2 1 CN-- df 69942 0x8026ab000 0x8026b5000 r-x 10 11 10 4 CN-- vn /usr/local/lib/libintl.so.8.1.4 69942 0x8026b5000 0x8028b5000 --- 0 0 2 0 CN-- df 69942 0x8028b5000 0x8028b6000 rw- 1 0 2 0 CN-- vn /usr/local/lib/libintl.so.8.1.4 69942 0x802c00000 0x803400000 rw- 218 0 1 0 C--- df 69942 0x7fffdfffe000 0x7fffdffff000 --- 0 0 0 0 ---- -- 69942 0x7ffffffdf000 0x7ffffffff000 rw- 10 0 1 0 C--D df 69942 0x7ffffffff000 0x800000000000 r-x 1 1 35 0 ---- ph --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Fri Mar 18 12:05:43 2016 Return-Path: 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 6A0F6AD539E for ; Fri, 18 Mar 2016 12:05:43 +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 3E39710F5 for ; Fri, 18 Mar 2016 12:05:43 +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 u2IC5h4c019786 for ; Fri, 18 Mar 2016 12:05:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Fri, 18 Mar 2016 12:05:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rblayzor@inoc.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 12:05:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #66 from Robert Blayzor --- backtrace from previous crash: #1 0x000000080120706d in __thr_fork () at /.amd_mnt/juno/pub/FreeBSD/10-STABLE/lib/libthr/thread/thr_fork.c:203 rtld_locks =3D {-4800, 32767, -4760, 32767, -4792, 32767, 3, 0} curthread =3D (struct pthread *) 0x803006400 cancelsave =3D 0 ret =3D 0 errsave =3D 4 #2 0x0000000000428c54 in handle_smtp_call (listen_sockets=3D0x803065140, listen_socket_count=3D4, accept_socket=3D7, accepted=3D0x7fffffffcd38) at daemon.c:355 pid =3D 32767 interface_sockaddr =3D {v4 =3D {sin_len =3D 28 '\034', sin_family = =3D 28 '\034', sin_port =3D 6400, sin_addr =3D {s_addr =3D 0}, sin_zero =3D 0x7fff= ffffc9a0 "&\a=C3=B0X\001\020"}, v6 =3D { sin6_len =3D 28 '\034', sin6_family =3D 28 '\034', sin6_port =3D 6400, sin6_flowinfo =3D 0, sin6_addr =3D {__u6_addr =3D {__u6_addr8 =3D 0x7ffffff= fc9a0 "&\a=C3=B0X\001\020", __u6_addr16 =3D 0x7fffffffc9a0, __u6_addr32 =3D 0x7fffffffc9a0}}, sin6_scope_id =3D 0}, v0 =3D {sa_len =3D 28 '\034', sa_family =3D 28 '\034'= , sa_data =3D 0x7fffffffc99a ""}} ifsize =3D 28 dup_accept_socket =3D 9 max_for_this_host =3D 10 wfsize =3D 100 wfptr =3D 22 use_log_write_selector =3D 1980 whofrom =3D (uschar *) 0x803065e30 "[2607:f058:110:2::f:0]" reset_point =3D (void *) 0x803065e00 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Fri Mar 18 23:35:52 2016 Return-Path: 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 0715AAD50B4 for ; Fri, 18 Mar 2016 23:35:52 +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 EBE957A1 for ; Fri, 18 Mar 2016 23:35:51 +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 u2INZpvp033134 for ; Fri, 18 Mar 2016 23:35:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Fri, 18 Mar 2016 23:35:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 23:35:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #67 from John Baldwin --- Sorry for another possible hail mary, but I've noticed that many of your fa= ults are in the thread library. There were several changes to libthr between 10= .1 and 10.2. They should all be bug fixes (in particular fixes to allow applications to dlopen() an object that uses libthr). If these changes to libthr are relevant then there are a few things to investigate and/or try: 1) Can you run ldd on your dovecot and exim binaries to see if they are directly linked against libthr? 2) Do you know if your binaries are loading any "plugins" (e.g. SASL auth mechanisms, milters (I know postfix and sendmail can both use milters for things like greylisting, etc.))? If you are, are any of your plugins linked against libthr? If the answer to 1) is no, then the first thing to possibly try is to set LD_PRELOAD=3Dlibthr.so.3 in the environment of the dovecot and exim binarie= s when you start them up. (If using rc.d scripts you can do this via foo_env variables in rc.conf.) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Fri Mar 18 23:47:04 2016 Return-Path: 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 94880AD561E for ; Fri, 18 Mar 2016 23:47:04 +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 85734C8F for ; Fri, 18 Mar 2016 23:47:04 +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 u2INl4Xs056151 for ; Fri, 18 Mar 2016 23:47:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Fri, 18 Mar 2016 23:47:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rblayzor@inoc.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2016 23:47:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #68 from Robert Blayzor --- Exim most certainly is linked directly... ldd /usr/local/sbin/exim | grep thr libthr.so.3 =3D> /lib/libthr.so.3 (0x8011f5000) Also many of the dovecot libs are linked against libthr as well... ldd /usr/local/lib/dovecot/libdovecot* | grep thr libthr.so.3 =3D> /lib/libthr.so.3 (0x801fb0000) libthr.so.3 =3D> /lib/libthr.so.3 (0x801fb0000) libthr.so.3 =3D> /lib/libthr.so.3 (0x801fb0000) libthr.so.3 =3D> /lib/libthr.so.3 (0x801b91000) libthr.so.3 =3D> /lib/libthr.so.3 (0x801b91000) libthr.so.3 =3D> /lib/libthr.so.3 (0x801b91000) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Sat Mar 19 14:44:09 2016 Return-Path: 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 84F28AD4B9E for ; Sat, 19 Mar 2016 14:44:09 +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 757E3F3E for ; Sat, 19 Mar 2016 14:44:09 +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 u2JEi91m062028 for ; Sat, 19 Mar 2016 14:44:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 208138] process freezes in STOP state and can't be killed Date: Sat, 19 Mar 2016 14:44:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new 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 Some People X-Bugzilla-Who: robert.ayrapetyan@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 14:44:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208138 Bug ID: 208138 Summary: process freezes in STOP state and can't be killed Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: threads Assignee: freebsd-threads@FreeBSD.org Reporter: robert.ayrapetyan@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Hello! I've started to observe a very strange behavior on my desktop PC (never seen anything like that using FreeBSD as a desktop OS for more than 5 years). Two things changed since I've started to observe problems: 1. A new PC (HP Z440) setup 2. Updated OS (FreeBSD 10.2) At some moment some process freezes and can't be killed\removed. So far this happened with firefox, thunderbird and virtualbox. Only OS restart helps to remove such process from a list. It's a really annoying to have e.g. multiple firefox tabs in the panel which are dead. Details are given below: >uname -a FreeBSD work-pc 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14 01:3= 2:46 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERI= C=20 amd64 >uname -UK 1002000 1002000 >ps aux | grep firefox robert 1022 0.0 4.1 1102920 676568 v0 T Mon03PM 101:01.17 firefox -profile /portable/firefox/robert >procstat -k 1022 PID TID COMM TDNAME KSTACK=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 1022 100281 firefox Timer mi_switch sleepq_timedwait_s= ig _sleep umtxq_sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall=20 1022 100428 firefox DOM Worker mi_switch thread_suspend_swi= tch thread_single exit1 sigexit postsig ast Xfast_syscall=20 >procstat -i 1022 PID COMM SIG FLAGS 1022 firefox HUP --C 1022 firefox INT --C 1022 firefox QUIT -I- 1022 firefox ILL --C 1022 firefox TRAP --- 1022 firefox ABRT --C 1022 firefox EMT --- 1022 firefox FPE -I- 1022 firefox KILL --- 1022 firefox BUS --- 1022 firefox SEGV --C 1022 firefox SYS --- 1022 firefox PIPE -I- 1022 firefox ALRM --- 1022 firefox TERM P-- 1022 firefox URG -I- 1022 firefox STOP --- 1022 firefox TSTP --- 1022 firefox CONT --- 1022 firefox CHLD -I- 1022 firefox TTIN --- 1022 firefox TTOU --- 1022 firefox IO -I- 1022 firefox XCPU --- 1022 firefox XFSZ --- 1022 firefox VTALRM --C 1022 firefox PROF --- 1022 firefox WINCH -I- 1022 firefox INFO -I- 1022 firefox USR1 --- 1022 firefox USR2 --- 1022 firefox 32 --C ... 1022 firefox 65 --C 1022 firefox 66 --C 1022 firefox 67 --C pkill CONT 1022 pkill KILL 1022 produces no effect. There are no new messages in /var/log/messages. More info (stacks for 2 threads behind STOPped process 1022) (kgdb) thread 337 [Switching to thread 337 (Thread 100281)]#0 sched_switch ( td=3D0xfffff800b429d000, newtd=3D, flags=3D) at /usr/src/sys/kern/sched_ule.c:1945 1945 cpuid =3D PCPU_GET(cpuid); (kgdb) bt #0 sched_switch (td=3D0xfffff800b429d000, newtd=3D, flags=3D) at /usr/src/sys/kern/sched_ule.c:1945 #1 0xffffffff80952121 in mi_switch (flags=3D517, newtd=3D0x0) at /usr/src/sys/kern/kern_synch.c:491 #2 0xffffffff80990deb in sleepq_timedwait_sig (wchan=3D, pri=3D) at /usr/src/sys/kern/subr_sleepqueue.c:578 #3 0xffffffff80951af8 in _sleep (ident=3D0xfffff80011bd7400, lock=3D0xffffffff815c6ee0, priority=3D, wmesg=3D0xffffffff80fcb076 "uwait", sbt=3D, pr=3D, flags=3D) at /usr/src/sys/kern/kern_synch.c:249 #4 0xffffffff80966195 in umtxq_sleep (uq=3D0xfffff80011bd7400, wmesg=3D0xffffffff80fcb076 "uwait", abstime=3D0xfffffe0464912900) at /usr/src/sys/kern/kern_umtx.c:780 #5 0xffffffff80969007 in do_wait (td=3D, addr=3D, id=3D, timeout=3D, compat32=3D, is_private=3D) at /usr/src/sys/kern/kern_umtx.c:12= 47 #6 0xffffffff8096d473 in __umtx_op_wait_uint_private ( td=3D, uap=3D) at /usr/src/sys/kern/kern_umtx.c:3494 #7 0xffffffff80d4b3e7 in amd64_syscall (td=3D0xfffff800b429d000, traced=3D= 0) at subr_syscall.c:134 ---Type to continue, or q to quit--- #8 0xffffffff80d30acb in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:396 #9 0x000000080119fe1c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) thread 338 [Switching to thread 338 (Thread 100428)]#0 sched_switch ( td=3D0xfffff801108324a0, newtd=3D, flags=3D) at /usr/src/sys/kern/sched_ule.c:1945 1945 cpuid =3D PCPU_GET(cpuid); (kgdb) bt #0 sched_switch (td=3D0xfffff801108324a0, newtd=3D, flags=3D) at /usr/src/sys/kern/sched_ule.c:1945 #1 0xffffffff80952121 in mi_switch (flags=3D266, newtd=3D0x0) at /usr/src/sys/kern/kern_synch.c:491 #2 0xffffffff80959e00 in thread_suspend_switch (td=3D0xfffff801108324a0, p=3D0xfffff800112a8000) at /usr/src/sys/kern/kern_thread.c:947 #3 0xffffffff809599f5 in thread_single (p=3D0xfffff800112a8000, mode=3D1) at /usr/src/sys/kern/kern_thread.c:740 #4 0xffffffff8090c75e in exit1 (td=3D0xfffff801108324a0, rv=3D15) at /usr/src/sys/kern/kern_exit.c:244 #5 0xffffffff8094bf85 in sigexit (td=3D0xfffff801108324a0, sig=3D15) at /usr/src/sys/kern/kern_sig.c:2974 #6 0xffffffff8094c826 in postsig (sig=3D) at /usr/src/sys/kern/kern_sig.c:2877 #7 0xffffffff809959c7 in ast (framep=3D) at /usr/src/sys/kern/subr_trap.c:281 #8 0xffffffff80d30b30 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:421 #9 0x000000080146e64a in ?? () --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Sat Mar 19 14:48:26 2016 Return-Path: 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 52423AD4E73 for ; Sat, 19 Mar 2016 14:48:26 +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 42FE71240 for ; Sat, 19 Mar 2016 14:48:26 +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 u2JEmQ4U068384 for ; Sat, 19 Mar 2016 14:48:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 208138] process freezes in STOP state and can't be killed Date: Sat, 19 Mar 2016 14:48:26 +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 Some People X-Bugzilla-Who: robert.ayrapetyan@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 14:48:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208138 --- Comment #1 from robert.ayrapetyan@gmail.com --- A similar (and seems forgotten) issue - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201892 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Sat Mar 19 18:53:42 2016 Return-Path: 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 13469AD5931 for ; Sat, 19 Mar 2016 18:53:42 +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 044E9B08 for ; Sat, 19 Mar 2016 18:53:42 +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 u2JIrfJk059212 for ; Sat, 19 Mar 2016 18:53:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Sat, 19 Mar 2016 18:53:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 18:53:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #69 from John Baldwin --- (In reply to Robert Blayzor from comment #68) Ok. Some of the changes in 10.2 fixed problems related to loading libthr.s= o.3 at runtime after the binary had started (which is why I asked my question).= I think that my suggestion of using LD_PRELOAD would not be a useful test giv= en your reply. It might still be useful to try putting a 10.1 libthr in your = 10.2 image to see if just swapping out libthr fixes the issue. If it does it at least helps narrow down where the problem lies. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Sat Mar 19 20:08:35 2016 Return-Path: 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 9A2BAAD6D71 for ; Sat, 19 Mar 2016 20:08:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 84A61A64 for ; Sat, 19 Mar 2016 20:08:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8066AAD6D70; Sat, 19 Mar 2016 20:08:35 +0000 (UTC) Delivered-To: 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 8004AAD6D6F for ; Sat, 19 Mar 2016 20:08:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F3A21A62; Sat, 19 Mar 2016 20:08:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u2JK8QOb085133 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 19 Mar 2016 22:08:27 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u2JK8QOb085133 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u2JK8QqW085122; Sat, 19 Mar 2016 22:08:26 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 19 Mar 2016 22:08:26 +0200 From: Konstantin Belousov To: threads@freebsd.org Cc: jilles@freebsd.org Subject: Removing the pid 1 code Message-ID: <20160319200826.GF1741@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 20:08:35 -0000 We have very special code executed during the libthr initialisation, which attempts to set up session and controlling terminal when running as pid 1. I do not see why do we need this, e.g. why behaviour of a program must be different due to the presence of libthr and running as pid 1. The code is there from 1998' libc_r. Please either provide arguments why should we do that, or agree with the following change. I decided to pre-resolve getpid() just in case, as it is done by the current code, but even this is probably not neccessary. diff --git a/lib/libthr/thread/thr_init.c b/lib/libthr/thread/thr_init.c index 3c81299..f9f845b 100644 --- a/lib/libthr/thread/thr_init.c +++ b/lib/libthr/thread/thr_init.c @@ -305,7 +305,7 @@ _thread_init_hack(void) void _libpthread_init(struct pthread *curthread) { - int fd, first, dlopened; + int first, dlopened; /* Check if this function has already been called: */ if ((_thr_initial != NULL) && (curthread == NULL)) @@ -321,27 +321,6 @@ _libpthread_init(struct pthread *curthread) memcpy(__thr_jtable, jmp_table, sizeof(jmp_table)); __thr_interpose_libc(); - /* - * Check for the special case of this process running as - * or in place of init as pid = 1: - */ - if ((_thr_pid = getpid()) == 1) { - /* - * Setup a new session for this process which is - * assumed to be running as root. - */ - if (setsid() == -1) - PANIC("Can't set session ID"); - if (revoke(_PATH_CONSOLE) != 0) - PANIC("Can't revoke console"); - if ((fd = __sys_openat(AT_FDCWD, _PATH_CONSOLE, O_RDWR)) < 0) - PANIC("Can't open console"); - if (setlogin("root") == -1) - PANIC("Can't set login to root"); - if (_ioctl(fd, TIOCSCTTY, (char *) NULL) == -1) - PANIC("Can't set controlling terminal"); - } - /* Initialize pthread private data. */ init_private(); diff --git a/lib/libthr/thread/thr_rtld.c b/lib/libthr/thread/thr_rtld.c index cb20098..6c407d1 100644 --- a/lib/libthr/thread/thr_rtld.c +++ b/lib/libthr/thread/thr_rtld.c @@ -227,6 +227,7 @@ _thr_rtld_init(void) _rtld_atfork_post(NULL); _malloc_prefork(); _malloc_postfork(); + getpid(); syscall(SYS_getpid); /* mask signals, also force to resolve __sys_sigprocmask PLT */