From owner-freebsd-threads@freebsd.org Mon Feb 29 11:14:47 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 54BDCAB80B3 for ; Mon, 29 Feb 2016 11:14:47 +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 3743894F for ; Mon, 29 Feb 2016 11:14:47 +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 u1TBEkLw007855 for ; Mon, 29 Feb 2016 11:14:47 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, 29 Feb 2016 11:14:47 +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: version 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.20 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 11:14:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 Robert Blayzor changed: What |Removed |Added ---------------------------------------------------------------------------- Version|10.2-RELEASE |10.3-BETA2 --- Comment #54 from Robert Blayzor --- pid 852 comm exim: signal 11 err 7 code 2 type 12 addr 0x7fffffffc7b8 rsp 0x7fffffffc7c0 rip 0x801206f3e Failed to write core file for process exim (error 14) pid 852 (exim), uid 26: exited on signal 11 procstat -v /var/spool/tmp/exim.core PID START END PRT RES PRES REF SHD FL TP P= ATH 852 0x400000 0x560000 r-x 299 310 2 1 CN-- vn /usr/local/sbin/exim 852 0x760000 0x76a000 rw- 10 0 1 0 CN-- vn /usr/local/sbin/exim 852 0x76a000 0x779000 rw- 5 5 1 0 CN-- df 852 0x800760000 0x80077e000 r-x 30 30 34 0 CN-- vn /libexec/ld-elf.so.1 852 0x80077e000 0x800785000 rw- 7 7 1 0 CN-- df 852 0x800787000 0x8007b7000 rw- 40 40 1 0 CN-- df 852 0x80097d000 0x80097f000 rw- 2 2 1 0 CN-- df 852 0x80097f000 0x80098d000 r-x 8 9 6 3 CN-- vn 852 0x80098d000 0x800b8d000 --- 0 0 1 0 CN-- df 852 0x800b8d000 0x800b8e000 rw- 1 0 1 0 CN-- vn 852 0x800b8e000 0x800b9f000 rw- 0 0 0 0 ---- -- 852 0x800b9f000 0x800bc8000 r-x 41 41 8 4 CN-- vn 852 0x800bc8000 0x800dc7000 --- 0 0 1 0 CN-- df 852 0x800dc7000 0x800dc8000 rw- 1 0 1 0 CN-- vn 852 0x800dc8000 0x800dd8000 r-x 13 14 18 9 CN-- vn 852 0x800dd8000 0x800fd8000 --- 0 0 1 0 CN-- df 852 0x800fd8000 0x800fd9000 rw- 1 0 1 0 CN-- vn 852 0x800fd9000 0x800fdb000 rw- 0 0 0 0 ---- -- 852 0x800fdb000 0x800ff3000 r-x 15 17 2 1 CN-- vn 852 0x800ff3000 0x8011f3000 --- 0 0 1 0 CN-- df 852 0x8011f3000 0x8011f5000 rw- 2 0 1 0 CN-- vn 852 0x8011f5000 0x80120d000 r-x 24 25 25 12 CN-- vn /lib/libthr.so.3 852 0x80120d000 0x80140d000 --- 0 0 1 0 CN-- df 852 0x80140d000 0x80140e000 rw- 1 0 1 0 CN-- vn /lib/libthr.so.3 852 0x80140e000 0x80141a000 rw- 12 12 1 0 CN-- df 852 0x80141a000 0x801445000 r-x 35 38 4 2 CN-- vn 852 0x801445000 0x801645000 --- 0 0 1 0 CN-- df 852 0x801645000 0x801648000 rw- 3 0 1 0 CN-- vn 852 0x801648000 0x80181d000 r-x 368 376 2 1 CN-- vn 852 0x80181d000 0x801a1c000 --- 0 0 1 0 CN-- df 852 0x801a1c000 0x801a25000 rw- 9 0 1 0 CN-- vn 852 0x801a25000 0x801a88000 r-x 80 90 26 13 CN-- vn /usr/lib/libssl.so.7 852 0x801a88000 0x801c88000 --- 0 0 1 0 CN-- df 852 0x801c88000 0x801c92000 rw- 10 0 1 0 CN-- vn /usr/lib/libssl.so.7 852 0x801c92000 0x801e5f000 r-x 461 501 30 15 CN-- vn /lib/libcrypto.so.7 852 0x801e5f000 0x80205f000 --- 0 0 1 0 CN-- df 852 0x80205f000 0x802087000 rw- 40 0 1 0 CN-- vn /lib/libcrypto.so.7 852 0x802087000 0x802089000 rw- 1 1 1 0 CN-- df 852 0x802089000 0x8020fe000 r-x 43 43 7 3 CN-- vn 852 0x8020fe000 0x8022fd000 --- 0 0 1 0 CN-- df 852 0x8022fd000 0x8022fe000 rw- 1 0 1 0 CN-- vn 852 0x8022fe000 0x802476000 r-x 376 387 67 33 CN-- vn /lib/libc.so.7 852 0x802476000 0x802675000 --- 0 0 1 0 CN-- df 852 0x802675000 0x802681000 rw- 12 0 1 0 CN-- vn /lib/libc.so.7 852 0x802681000 0x8026ab000 rw- 11 11 1 0 CN-- df 852 0x8026ab000 0x8026b5000 r-x 10 11 9 4 CN-- vn 852 0x8026b5000 0x8028b5000 --- 0 0 1 0 CN-- df 852 0x8028b5000 0x8028b6000 rw- 1 0 1 0 CN-- vn 852 0x802c00000 0x803400000 rw- 218 218 1 0 CN-- df 852 0x7fffdfffe000 0x7fffdffff000 --- 0 0 0 0 ---- -- 852 0x7ffffffdf000 0x7ffffffff000 rw- 10 0 1 0 C--D df 852 0x7ffffffff000 0x800000000000 r-x 1 1 36 0 ---- ph --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Mon Feb 29 11:17: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 E26D6AB815E for ; Mon, 29 Feb 2016 11:17: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 D0F45A76 for ; Mon, 29 Feb 2016 11:17: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 u1TBHfRH012192 for ; Mon, 29 Feb 2016 11:17: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: Mon, 29 Feb 2016 11:17: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: 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.20 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 11:17:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #55 from Robert Blayzor --- bt from last=20 (gdb) bt full #0 __thr_fork () at /.amd_mnt/juno/pub/FreeBSD/10-STABLE/lib/libthr/thread/thr_fork.c:186 rtld_locks =3D Cannot access memory at address 0x7fffffffc7d0 Current language: auto; currently minimal (gdb) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Mon Feb 29 12:59:48 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 D0445AB7FC7 for ; Mon, 29 Feb 2016 12:59:48 +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 C19B71C19 for ; Mon, 29 Feb 2016 12:59:48 +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 u1TCxj3G081915 for ; Mon, 29 Feb 2016 12:59:48 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: Mon, 29 Feb 2016 12:59:46 +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: me.freebsd@lelf.lu 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: cc 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.20 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 12:59:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200992 Antonio Nikishaev changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |me.freebsd@lelf.lu --- Comment #25 from Antonio Nikishaev --- This bug is rather major. I'm seeing the same issue with DigitalOcean instances (10.2-RELEASE(!)). Riak2 nodes randomly hang up every several days. % uname -a FreeBSD riak-freebsd-8gb-nyc3-01 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r2866= 66: Wed Aug 12 15:26:37 UTC 2015=20=20=20=20 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 % sudo procstat -k 76975 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 76975 101201 beam.smp - mi_switch sleepq_timedwait _cv_timedwait_sbt amd64_syscall Xfast_syscall=20 76975 101317 beam.smp - mi_switch thread_suspend_swi= tch thread_single exit1 sigexit postsig ast doreti_ast=20 % ps -auxw -p 76975 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND riak 76975 0.0 72.1 7524240 6030480 - T 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 0410BAB81A0 for ; Mon, 29 Feb 2016 15:14: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 E8CDE1C38 for ; Mon, 29 Feb 2016 15:13:59 +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 u1TFDxDK027224 for ; Mon, 29 Feb 2016 15:13:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 30464] [patch] pthread mutex attributes -- pshared Date: Mon, 29 Feb 2016 15:14: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: 4.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.20 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 15:14:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D30464 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emaste@freebsd.org --- Comment #6 from Ed Maste --- See r296162 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Mon Feb 29 15:14:48 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 508D5AB81EF for ; Mon, 29 Feb 2016 15:14:48 +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 417B51C86 for ; Mon, 29 Feb 2016 15:14:48 +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 u1TFEmT7028539 for ; Mon, 29 Feb 2016 15:14:48 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, 29 Feb 2016 15:14:48 +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.20 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 15:14:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #56 from Konstantin Belousov --- (In reply to Robert Blayzor from comment #55) The uprintf_signal data was useful, thanks. It is quite clean that the issue occured in the child after the multithreaded fork. An evidence is in the 'CN' flags (copy on write and need copy) for all map entries of the process, except the stack. The number of stacks mapped also suggests that the parent only had one thread executing during the fork. This is confirmed also by the backtrace from the core, but for different reasons I trust the core less. The fault occured on the stack access, as indicated by the fault address. What is very interesting is the error code 7, which is hardware data indicating that this was user-mode write to the page mapped read-only. Which is again consistent with the state after fork. What I do not understand is why page fault handler did not performed COW and changed the page permission to writeable, which it should, due to rw permission on the map entry. Could you, please, apply the attached debugging patch on top of the used source and provide me the same data as now, i.e. procstat -v code and kernel messages from the patch and uprintf_signal. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Mon Feb 29 15:16:03 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 E9A0AAB8233 for ; Mon, 29 Feb 2016 15:16:03 +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 DA5F01CD0 for ; Mon, 29 Feb 2016 15:16:03 +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 u1TFG3fG031007 for ; Mon, 29 Feb 2016 15:16:03 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, 29 Feb 2016 15:16: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: 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: attachments.created 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.20 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 15:16:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #57 from Konstantin Belousov --- Created attachment 167570 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D167570&action= =3Dedit Debugging patch to track source of KERN_PROTECTION_FAILURE --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Mon Feb 29 20:23:34 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 A3227AB9514 for ; Mon, 29 Feb 2016 20:23:34 +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 922A71E83 for ; Mon, 29 Feb 2016 20:23:34 +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 u1TKNYZJ008312 for ; Mon, 29 Feb 2016 20:23:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 199800] Thread Stack Size - Segmentation Fault Date: Mon, 29 Feb 2016 20:23:34 +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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: emaste@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.20 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 20:23:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199800 --- Comment #3 from Ed Maste --- Can you confirm that this is fixed either in 10.2+ or with LIBPTHREAD_BIGSTACK_MAIN? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Wed Mar 2 18:46:30 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 60E6EAC2E33 for ; Wed, 2 Mar 2016 18:46:30 +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 5161D1010 for ; Wed, 2 Mar 2016 18:46:30 +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 u22IkT6n051677 for ; Wed, 2 Mar 2016 18:46:30 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, 02 Mar 2016 18:46:30 +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.20 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2016 18:46:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200992 --- Comment #26 from commit-hook@freebsd.org --- A commit references this bug: Author: kib Date: Wed Mar 2 18:46:18 UTC 2016 New revision: 296320 URL: https://svnweb.freebsd.org/changeset/base/296320 Log: If callout_stop_safe() noted that the callout is currently executing, but next invocation is cancelled while migrating, sleepq_check_timeout() needs to be informed that the callout is stopped. Otherwise the thread switches off CPU and never become runnable, since running callout could have already raced with us, while the migrating and cancelled callout could be one which is expected to set TDP_TIMOFAIL flag for us. This contradicts with the expected behaviour of callout_stop() for other callers, which e.g. decrement references from the callout callbacks. Add a new flag CS_MIGRBLOCK requesting report of the situation as 'successfully stopped'. Reviewed by: jhb (previous version) Tested by: cognet, pho PR: 200992 Sponsored by: The FreeBSD Foundation MFC after: 2 weeks Differential revision: https://reviews.freebsd.org/D5221 Changes: head/sys/kern/kern_timeout.c head/sys/kern/subr_sleepqueue.c head/sys/sys/callout.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Thu Mar 3 10:58:05 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 F150FA9338A for ; Thu, 3 Mar 2016 10:58:05 +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 E2D79D79 for ; Thu, 3 Mar 2016 10:58:05 +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 u23Aw23K050070 for ; Thu, 3 Mar 2016 10:58:05 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: Thu, 03 Mar 2016 10:58:02 +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: hselasky@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: Thu, 03 Mar 2016 10:58:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200992 --- Comment #27 from Hans Petter Selasky --- Hi, I believe all of these callout quirks can be avoided by using a spinlock to proctect the thread callout like done in projects/hps_head. Has anyone trie= d to reproduce the issue with projects/hps_head, before making this patch? --HPS --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Fri Mar 4 00:39:50 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 57F0AA94920 for ; Fri, 4 Mar 2016 00:39:50 +0000 (UTC) (envelope-from bounce@ds.master-zen.com) Received: from worm2-48.rs.sucko.es (worm2-48.rs.sucko.es [77.246.189.43]) (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 EA8AD387 for ; Fri, 4 Mar 2016 00:39:49 +0000 (UTC) (envelope-from bounce@ds.master-zen.com) Date: Fri, 4 Mar 2016 00:37:08 +0100 DKIM-Filter: OpenDKIM Filter v2.9.2 worm2-48.rs.sucko.es E59827D21DCE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=master-zen.com; s=smtp; t=1457048228; bh=rbBSQr7g1mXOgqR/ybCPKnwkKtcCPGhtb+yiQw0Z+7w=; h=Date:List-Unsubscribe:To:From:Reply-to:Subject; b=nJDVtM+cQgi7739fGde1FgzG7Z1QlXQ3S9xCW3Wz1UHUimpiRBCvhcpXKlQA2zlt9 aQvHccYLVQJz3G9xOmPzjiQaG6aAmwNRcb6EONKsJ6ibpRRh3IJn5crvSbRclYBR+e 0K80wKQM4C1XjZPGWwpgpWFIqls+dIa6loKiPvvg= To: freebsd-threads@freebsd.org From: Quiz Reply-to: reply@master-zen.com Subject: =?UTF-8?Q?(1)_iPhone_6S_f=C3=BCr_Sie!?= Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 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, 04 Mar 2016 00:39:50 -0000 tu mejor oferta Um aus dem Abo-Liste abmelden, folgen Sie diesem Link: http://ds.luckies500.com/fur.php?c=%7B%22idCli%22%3A%221729%22%2C%22idCamp%22%3A%22919243%22%2C%22email%22%3A%22freebsd-threads%40freebsd.org%22%2C%22seg%22%3A%22nnvgo4jvga2tsmlskbzwg%3D%3D%3D%22%7D&at=1 From owner-freebsd-threads@freebsd.org Sat Mar 5 12:22:40 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 556E69DB0B6 for ; Sat, 5 Mar 2016 12:22:40 +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 466A330F for ; Sat, 5 Mar 2016 12:22:40 +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 u25CMdVB079188 for ; Sat, 5 Mar 2016 12:22: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: Sat, 05 Mar 2016 12:22: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: 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: Sat, 05 Mar 2016 12:22:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #58 from Robert Blayzor --- After both patches... pid 716 (dovecot), uid 0: exited on signal 11 (core dumped) (gdb) bt full #0 memcpy () at bcopy.S:65 No locals. #1 0x0000000800915484 in sig_handler (signo=3D20, si=3D0x7fffffffa9a0, context=3D0x7fffffffa630) at lib-signals.c:132 h =3D (struct signal_handler *) 0x8014198e0 saved_errno =3D 14 c =3D 0 '\0' tmp_si =3D {si_signo =3D 0, si_errno =3D 0, si_code =3D 0, si_pid = =3D 0, si_uid =3D 0, si_status =3D 0, si_addr =3D 0x0, si_value =3D {sival_int =3D 0, sival_ptr =3D 0x0, sigval= _int =3D 0, sigval_ptr =3D 0x0}, _reason =3D {_fault =3D {_trapno =3D 0}, _timer =3D {_timerid =3D 0, _ove= rrun =3D 0}, _mesgq =3D {_mqd =3D 0}, _poll =3D {_band =3D 0}, __spare__ =3D {__spare1__ =3D 0, __spare2__ =3D 0x7fffffffa5c8}}} #2 No symbol table info available. #3 0x0000000000411fc8 in _fini () No symbol table info available. #4 0x000000080061c9a8 in objlist_call_fini () at /.amd_mnt/juno/pub/FreeBSD/10-STABLE/libexec/rtld-elf/rtld.c:2354 list =3D (Objlist *) Cannot access memory at address 0x0 Current language: auto; currently asm (gdb) q dev@mta1 [/var/spool/tmp] sudo procstat -v /var/spool/tmp/dovecot.core PID START END PRT RES PRES REF SHD FL TP P= ATH 716 0x400000 0x417000 r-x 20 20 1 0 CN-- vn 716 0x617000 0x618000 rw- 1 1 1 0 C--- df 716 0x800617000 0x800635000 r-x 30 30 32 0 CN-- vn /libexec/ld-elf.so.1 716 0x800635000 0x800663000 rw- 36 36 1 0 C--- df 716 0x800834000 0x800836000 rw- 2 2 1 0 C--- df 716 0x800836000 0x800983000 r-x 225 231 34 17 CN-- vn /usr/local/lib/dovecot/libdovecot.so.0.0.0 716 0x800983000 0x800b82000 --- 0 0 1 0 CN-- df 716 0x800b82000 0x800b89000 rw- 7 0 1 0 C--- vn /usr/local/lib/dovecot/libdovecot.so.0.0.0 716 0x800b89000 0x800b8b000 rw- 2 0 1 0 C--- df 716 0x800b8b000 0x800d03000 r-x 376 387 63 31 CN-- vn /lib/libc.so.7 716 0x800d03000 0x800f02000 --- 0 0 1 0 CN-- df 716 0x800f02000 0x800f0e000 rw- 12 0 1 0 C--- vn /lib/libc.so.7 716 0x800f0e000 0x800f38000 rw- 15 15 1 0 C--- df 716 0x801000000 0x801800000 rw- 94 94 1 0 C--- df 716 0x7ffffffdf000 0x7ffffffff000 rw- 8 8 1 0 C--D df 716 0x7ffffffff000 0x800000000000 r-x 1 1 34 0 ---- ph (gdb) bt full #0 memcpy () at bcopy.S:65 No locals. #1 0x0000000800915484 in sig_handler (signo=3D20, si=3D0x7fffffffa9a0, context=3D0x7fffffffa630) at lib-signals.c:132 h =3D (struct signal_handler *) 0x8014198e0 saved_errno =3D 14 c =3D 0 '\0' tmp_si =3D {si_signo =3D 0, si_errno =3D 0, si_code =3D 0, si_pid = =3D 0, si_uid =3D 0, si_status =3D 0, si_addr =3D 0x0, si_value =3D {sival_int =3D 0, sival_ptr =3D 0x0, sigval= _int =3D 0, sigval_ptr =3D 0x0}, _reason =3D {_fault =3D {_trapno =3D 0}, _timer =3D {_timerid =3D 0, _ove= rrun =3D 0}, _mesgq =3D {_mqd =3D 0}, _poll =3D {_band =3D 0}, __spare__ =3D {__spare1__ =3D 0, __spare2__ =3D 0x7fffffffa5c8}}} #2 No symbol table info available. #3 0x0000000000411fc8 in _fini () No symbol table info available. #4 0x000000080061c9a8 in objlist_call_fini () at /.amd_mnt/juno/pub/FreeBSD/10-STABLE/libexec/rtld-elf/rtld.c:2354 list =3D (Objlist *) Cannot access memory at address 0x0 Current language: auto; currently asm --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Sat Mar 5 12:29:50 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 5F3AA9DB2EA for ; Sat, 5 Mar 2016 12:29:50 +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 504A6697 for ; Sat, 5 Mar 2016 12:29:50 +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 u25CTnSe088052 for ; Sat, 5 Mar 2016 12:29:50 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, 05 Mar 2016 12:29:50 +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: Sat, 05 Mar 2016 12:29:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #59 from Robert Blayzor --- Thinking about this a little, going out on a limb. The only thing that diff= ers on these servers compared to other diskless boot servers we have. (that use= the same read only NFS root) is they have a larger memory disks for "/var" when created from /etc/rc.initdiskless. /dev/md0 8.8M 3.8M 4.3M 47% /etc /dev/md1 457M 516K 420M 0% /var Because these are mail servers, /var may be a bit busier than on say DNS and web servers. (as /var/tmp is there, etc, temporary file writes from files b= eing scanned by viruses). I've never seen any "out of memory" errors or that mou= nt ever close to being anywhere near full; but I'm sure there are a lot of read/write going on. I know it's a stretch but it's the only thing I can think of that differs f= rom the other diskless servers that are setup the exact same way. This appears to be happening on only our mail servers, which consequently happen to be our busiest. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-threads@freebsd.org Sat Mar 5 16:51:24 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 4D5DDA09EED for ; Sat, 5 Mar 2016 16:51:24 +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 3EEABFAD for ; Sat, 5 Mar 2016 16:51:24 +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 u25GpNhx083944 for ; Sat, 5 Mar 2016 16:51:24 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, 05 Mar 2016 16:51:24 +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: Sat, 05 Mar 2016 16:51:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #60 from Konstantin Belousov --- (In reply to Robert Blayzor from comment #58) And where is uprintf_signal output, as well as the printfs from the debuggi= ng patch ? --=20 You are receiving this mail because: You are the assignee for the bug.=