From owner-freebsd-questions@FreeBSD.ORG Sun Feb 22 04:14:23 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 145708A8 for ; Sun, 22 Feb 2015 04:14:23 +0000 (UTC) Received: from mail.parts-unknown.org (mail.parts-unknown.org [IPv6:2001:470:67:119::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E558774A for ; Sun, 22 Feb 2015 04:14:22 +0000 (UTC) Received: by mail.parts-unknown.org (Postfix, from userid 1001) id 517F45B3BD21; Sat, 21 Feb 2015 20:14:21 -0800 (PST) Date: Sat, 21 Feb 2015 20:14:21 -0800 From: David Benfell To: cpet Subject: Re: why would I get a segmentation fault on one system but not the other? Message-ID: <20150222041421.GA36213@home.parts-unknown.org> References: <20150221224006.GA5501@home.parts-unknown.org> <09da5ec0816e098badc49432c802dc18@sdf.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline In-Reply-To: <09da5ec0816e098badc49432c802dc18@sdf.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: 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: Sun, 22 Feb 2015 04:14:23 -0000 --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 21, 2015 at 05:01:17PM -0600, cpet wrote: >=20 > You have 2 systems one running a different svn rev than the other, first= =20 > I would suggest before suggesting bad ram is to sync both to be equal,=20 > meaning the one that is failing to either upgrade or downgrade it. if=20 > it's seg faulting I would mem test that and replace failing module. >=20 The system experiencing the segfaults is new--and from a vendor that has previously shipped me a system with bad memory. So I think you'll understand if I reversed the order of your suggested steps. I haven't stopped the memory test yet. But it has been running for an hour and completed one pass without error. From what I can see on line, that's a pretty good sign. So, now the second step. The implication of what you're suggesting is fairly obviously that the segfaults are originating in the base system. I'm now worried about upgrading the old system (which is working fine and, oh, by the way, is the one that had originally been shipped with memory problems). If you're right, to upgrade it might break what is a (maybe not quite) perfectly good system. So how would I downgrade to the earlier revision? Thanks! --=20 David Benfell See https://parts-unknown.org/node/2 if you don't understand the attachment. --KsGdsel6WgEHnImy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJU6VedAAoJEBV64x4SNmAra2cQAIywKE2YxkCi6SJk1muLYcGC 1zO+4GDzwnXnhCxR2U1DoGdcWfPnjjZTHd0DVSfRYhiBZv6ujB5kPuifffDFNO14 mUfco+ioe5hjeQDGERYsv4PwHtL5PfyH42NvaaDi/6Jp+b6kfYIuAvwSeQ9q0lIB ynD2VQTuhYPjNjbSqv1dZJsfeUNe/jInskyHtO208YFzOD4qDeRxumWGXvgH9u9v IHVVrLH0OgvUX0mpw8dfPqUnVifX4Uk1Oblzs44P5dteSpOeog5EQqWoxtwPB1Xo nkwZMvIecH+m4fzhmR7I45CwSyrhYxPb2W8LRIXWkv56Cm50lxDzaXSXv2XLTl5J GMopIS/Cu21kx7/I/zCSDZiG4mAxhFeeCdKiBiQFYDITCtgke8D/02hAyCCBCZYz 59JjmC4shLVK8x/frzTsTbHtWZ6HqOrr5JgTknhNan5eH5LJf9Ti5D80nuNOwo8d p/hgouz2Iap0ejRw8XgM3B1SBBp4Z33u7YlMvx29QlVTKk72qslCjpizMQq5eP9q vWtg69fc+hP1sEr5hi4jpZv5JTjmzrNX/1gKvYuDaLMlfl5ow6fQQ6F43duAwXw+ Mw2PataWefFiJQNJAlQbUYhtrwIF1y/sAbhAO8ZuQBkQaUORHHQ221pvq92kaDhD CmoZ+cSmBc/OTvAmAMbS =JW8/ -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy--