Date: Mon, 22 Feb 2016 14:59:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-ukbBRpOhjh@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/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204426 --- Comment #49 from Robert Blayzor <rblayzor@inoc.net> --- VMWare ESXi 5.1u2 I have *NOT* seen this behavior on other VM's created on the same set of ESXi hosts. The common thread (difference) seems to be these are setup to be "diskless" boot VM's where their root filesystem is mounted RO / via NFS. (NetApp) I have bare metal hosts running 10.2 with no problem. But at the same time, I have VM hosts, which have a local disk (vmdk) which are fine, and they're on the same physical ESXI hosts. I'll set sysctl machdep.uprintf_signal as well. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204426-16-ukbBRpOhjh>