From owner-freebsd-questions@FreeBSD.ORG Sat Feb 21 23:01:20 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21A43395; Sat, 21 Feb 2015 23:01:20 +0000 (UTC) Received: from sdf.org (ma.sdf.org [192.94.73.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ma.sdf.org", Issuer "ma.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 015C6330; Sat, 21 Feb 2015 23:01:19 +0000 (UTC) Received: from ma.sdf.org (IDENT:U2FsdGVkX192Eo2/m3raNQIrIzA63HaltX7kTUcAsTM@ma.sdf.org [192.94.73.31]) by sdf.org (8.14.4/8.14.3) with ESMTP id t1LN1HQW007070; Sat, 21 Feb 2015 23:01:17 GMT MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 21 Feb 2015 17:01:17 -0600 From: cpet To: David Benfell Subject: Re: why would I get a segmentation fault on one system but not the =?UTF-8?Q?other=3F?= In-Reply-To: <20150221224006.GA5501@home.parts-unknown.org> References: <20150221224006.GA5501@home.parts-unknown.org> Message-ID: <09da5ec0816e098badc49432c802dc18@sdf.org> X-Sender: cpet@sdf.org User-Agent: Roundcube Webmail/1.0.1 Cc: freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2015 23:01:20 -0000 On 2015-02-21 16:40, David Benfell wrote: > Hi all, > > I am running into a segmentation fault that I don't know how to track > down. It appears on one system but not the other. It seems to afflict > both apache24 and php-fpm. > > apache logs lots of segementation faults but I don't have any idea > where they're coming from. > > When I try to start php-fpm it dies instantly with a segmentation > fault. I think it's one of the modules, but I don't know which one. > > And I'm absolutely baffled that this occurs on one system and not the > other. Both are fairly recent FreeBSD Stable. > > I do not see the segmentation faults (or at least not in such a dire > way) on: > > 10.1-STABLE > FreeBSD home.parts-unknown.org 10.1-STABLE FreeBSD 10.1-STABLE #0 > r278923: Tue Feb 17 15:27:20 PST 2015 > root@home.parts-unknown.org:/usr/obj/usr/src/sys/GENERIC amd64 > > I do see them on: > > 10.1-STABLE > FreeBSD vegan.parts-unknown.org 10.1-STABLE FreeBSD 10.1-STABLE #0 > r278934: Wed Feb 18 09:11:24 UTC 2015 > root@home.parts-unknown.org:/usr/obj/usr/src/sys/GENERIC amd64 You have 2 systems one running a different svn rev than the other, first I would suggest before suggesting bad ram is to sync both to be equal, meaning the one that is failing to either upgrade or downgrade it. if it's seg faulting I would mem test that and replace failing module.