Date: Mon, 22 Feb 2016 14:02:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-aUwxBsCVg3@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #46 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to Robert Blayzor from comment #43) So are you binaries and libs executed from NFS mount ? Could you try to mo= unt them statically instead of using automounter ? Even better, try with a loc= al filesystem. Another thing to do is to set sysctl machdep.uprintf_signal to 1. I would = need the matching output on the failure and procstat -v output from the (corrupt= ed) core. Do you run ntpd ? Do failures continue to appear if you stop both ntpd and automounter ? --=20 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-204426-16-aUwxBsCVg3>