From owner-freebsd-scsi@freebsd.org  Fri Mar  4 10:59:03 2016
Return-Path: <owner-freebsd-scsi@freebsd.org>
Delivered-To: freebsd-scsi@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 237E39DAA1E
 for <freebsd-scsi@mailman.ysv.freebsd.org>;
 Fri,  4 Mar 2016 10:59:03 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com
 [195.16.151.151])
 (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 D46AD91E
 for <freebsd-scsi@freebsd.org>; Fri,  4 Mar 2016 10:59:02 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from [172.16.8.96] (izaro.sarenet.es [192.148.167.11])
 by proxypop01.sare.net (Postfix) with ESMTPSA id B15CF9DD2D9;
 Fri,  4 Mar 2016 11:58:58 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: mpr(4) SAS3008 Repeated Crashing
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <56D95266.301@multiplay.co.uk>
Date: Fri, 4 Mar 2016 11:58:58 +0100
Cc: Scott Long <scott4long@yahoo.com>, FreeBSD-scsi <freebsd-scsi@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC3018EA-A1F3-4C7C-A179-58553457A938@sarenet.es>
References: <56D5FDB8.8040402@freebsd.org> <56D612FA.6090909@multiplay.co.uk>
 <A8859ECA-0B58-42A8-AA49-DF6AA3D52CC6@sarenet.es>
 <E74F5225-1EA8-4B60-ADDC-7B13E1003184@yahoo.com>
 <D7E0BCCE-EB44-4EF9-8F17-474C162F7D7C@sarenet.es>
 <56D805FD.50500@multiplay.co.uk>
 <F9B68610-12C6-4D32-88CA-A34A185F9AD1@sarenet.es>
 <F5E05621-FF84-4BED-B1A7-3252715CD53B@yahoo.com>
 <B2147AEC-2831-443C-8FA0-4148B37AAF95@sarenet.es>
 <56D95266.301@multiplay.co.uk>
To: Steven Hartland <killing@multiplay.co.uk>
X-Mailer: Apple Mail (2.3112)
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi/>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2016 10:59:03 -0000


> On 04 Mar 2016, at 10:16, Steven Hartland <killing@multiplay.co.uk> =
wrote:
>=20
> Its very rare but we've also seen this type of behaviour from a =
failing Intel CPU. There was no other indication the CPU had an issue, =
which one might expect, so just wanted to make you aware of the =
possibility.
>=20
> That said the most common cause of this we've seen, when its not a =
common disk or disks, is a bad backplane or cabling to the backplane.

Now I=E2=80=99m really curious!

How did you determine that it was the CPU? And what kind of issue was it =
causing? Noise in the power rails? Interference?





Borja.