Date: Mon, 28 Mar 2016 12:09:48 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-sT3Oolh7Ga@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 #71 from Robert Blayzor <rblayzor@inoc.net> --- I will double check the sysctl and set if not the case. It may not have persisted across reboot of the last kernel. We want to avoid upgrading major revs of the hypervisor as we have other VM= 's that do not have NFS diskless root that we have no problems with. The only difference between these hosts and other hosts on the same hypervi= sor is these boot with no local (virtual) disk for the root FS; only tmp/swap. We have no 3rd party modules loaded. --=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-sT3Oolh7Ga>