From owner-freebsd-threads@freebsd.org  Mon Feb  1 13:06:10 2016
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 72BFFA74AEE
 for <freebsd-threads@mailman.ysv.freebsd.org>;
 Mon,  1 Feb 2016 13:06:10 +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 5BFBABE1
 for <freebsd-threads@FreeBSD.org>; Mon,  1 Feb 2016 13:06:10 +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 u11D6Ava015333
 for <freebsd-threads@FreeBSD.org>; Mon, 1 Feb 2016 13:06:10 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, 01 Feb 2016 13:06:10 +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.2-RELEASE
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: cc
Message-ID: <bug-204426-16-AsR77aXn7q@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204426-16@https.bugs.freebsd.org/bugzilla/>
References: <bug-204426-16@https.bugs.freebsd.org/bugzilla/>
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 <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: Mon, 01 Feb 2016 13:06:10 -0000

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

Konstantin Belousov <kib@FreeBSD.org> changed:

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

--- Comment #23 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to rblayzor from comment #22)
This smells like a pager error.  You mentioned somewhere that the images for
the programs which failed are located on NFS volume ?  What is in dmesg ?

I believe that pager somehow fails to page in, and this causes both access
errors in the live processes (SIGSEGV) and EFAULT when kernel reads process
mappings to dump them into core files.

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