Date: Tue, 26 Jan 2016 18:51:59 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-7NYF1Q04Gm@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 #11 from rblayzor@inoc.net --- Since we're using a FreeBSD diskless boot and NFS_ROOT I normally buildworld (and kernel) from sources and install in a new NFS_ROOT path, then boot the diskless servers with the new root path. Before booting however, I will also force rebuild (portupgrade -af) everyth= ing against the new version of FreeBSD (kernel/userland, libs, etc). So the binaries that are crashing *are* being rebuilt under FreeBSD 10.2. We never experienced this in 10.1 and in fact, we even rolled back and boot= ed one of the diskless servers using an old NFS_ROOT path with 10.1 (same vers= ions of Exim and Dovecot) and those have not crashed. Usually I will experience these types of seg faults on every VM server at least once a week. (current= ly these servers are lightly loaded because of this issue). Normally I would have no problem believing this is an application but since= it does not appear to happen on 10.1 and only on 10.2, coupled with the fact I= 'm seeing similar crashes on two different applications that were otherwise running fine is very suspect.=20 The applications are compiled with debugging symbols, but the crash always happens in a system library. I've contacted both Dovecot and Exim teams on these crashes and both agreed that it seemed to be some type of system libr= ary issue. I'm not ruling out that it may be something with our install, but it's fair= ly straight forward FreeBSD diskless install. Running out of places to look. --=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-7NYF1Q04Gm>