From owner-freebsd-questions@freebsd.org Mon Apr 18 14:59:07 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 811E9B13F64 for ; Mon, 18 Apr 2016 14:59:07 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (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 2157D1732 for ; Mon, 18 Apr 2016 14:59:07 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from ox-dell39.ox.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id C24FB11C14 for ; Mon, 18 Apr 2016 14:59:02 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/C24FB11C14; dkim=none; dkim-atps=neutral Subject: Re: FreeBSD Crashes Intermittently !! To: freebsd-questions@freebsd.org References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> From: Matthew Seaman Message-ID: Date: Mon, 18 Apr 2016 15:58:56 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ntLkTImdkjEBPXD7tb3mpPbj4vd05b02t" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2016 14:59:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ntLkTImdkjEBPXD7tb3mpPbj4vd05b02t Content-Type: multipart/mixed; boundary="tXvPUEkg1L9RWjFIxQ3VoXrLmoAmrFCsf" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: Subject: Re: FreeBSD Crashes Intermittently !! References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> In-Reply-To: --tXvPUEkg1L9RWjFIxQ3VoXrLmoAmrFCsf Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04/18/16 15:28, shahzaib mushtaq wrote: > Hi again, got back after a long time. So yes, we've move to new Dell R5= 10 > Hardware now. Here is the specs : >=20 > DELL R510 > 2 x L5520 > 64GB RAM > 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) > FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD 10.2-RELEASE-p14 #= 0: > Wed Mar 16 20:46:12 UTC 2016 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > amd64 >=20 > After 9days of uptime, server again got crashed with following error in= > crash log : See where it says this in your crash log: Hardware event. This is not a software error Unfortunately your 'new' server is broken. I say 'new' because the R510 is an 11th generation product no longer available from Dell (they're on 13th generation kit now) -- it must be several years old at least. Try running memtest86 on it and see how long it survives. If memtest86 says something is broken, then it's pretty definitive. (Although when memtest86 doesn't say 'broken', that doesn't necessarily mean it is OK -- there are failure conditions that memtest86 doesn't pick up on.) According to the output you posted one of the CPUs has gone kaput. If this machine has multiple physical CPU packages, you might be able to get it to run reliably by taking out the broken one. Identifying which one that is might be tricky, but if all else fails you can do it be a process of elimination. Be aware though that removing a CPU pacckage may mean you need to juggle the RAM about, as it's fairly common for some of the RAM slots to be tied to a specific CPU package. Cheers, Matthew --tXvPUEkg1L9RWjFIxQ3VoXrLmoAmrFCsf-- --ntLkTImdkjEBPXD7tb3mpPbj4vd05b02t Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXFPYwAAoJEABRPxDgqeTn5sUP/A2MMtIXDaa37KaYfPSNJpL1 3Vz8RCFTwhLqn+jyfbEYPEAwXQ+f23bnSAxtflVqF9NbPkZVqFTCU3USfPc7ed5V ml3nSQh5l6k3sFYu2EMtD/mFzNzucWpYlnAD8LIZmGvjg5YrC9Xf/GnX7D/3jG+f K9onlWD6+62wCOGQI1UEVY+3KRcmJcrovIVV1nEGZSRkuFbsiaiSFV//CUnfQQdf rX/+0LFWtkF/I+qdmFIubOUHA0BaPDJ8DXGQJJgu7Gq/nFT9aHYhPmlNmXcIWiqf 6UUNAs0QTAqFvm5CaV4MGKHfC3wVcx04bqpaetAOePJfF+T5My7e3wDKGf/j0ftO XWhyIRr6t3Lppu2Q+SNAftlT97MHdZZLAu6mPDdYG9CnsuXcL4UVbaQY2HPD8wJW gnGROJ4iNCRq5zDp+7qFyQMQe1iKW6/b00wLVTLGTue0pFr2uyLH05h/enFPzWed LBCqQf74HcGspLD4Wh77i6WTa+mfMcEl+u3R9pnNAqaVp8Ic0p1QATq8NlAg3OUT 6J0C1Pk1P/ty1N5mYoVCxwsy5mIje7hgeIp7UZ0Ta44WXCdv5wonJcIyqVukn7hG SQP8UNgmo2fP6WrVCRdgIi0shZQ4R7FNfKGdP3SsavnGL/lyA4GFX7o/nSzEFhjn BzS0wFjwCkCFVi68nYst =7405 -----END PGP SIGNATURE----- --ntLkTImdkjEBPXD7tb3mpPbj4vd05b02t--