Date: Fri, 4 Mar 2016 11:58:58 +0100 From: Borja Marcos <borjam@sarenet.es> To: Steven Hartland <killing@multiplay.co.uk> Cc: Scott Long <scott4long@yahoo.com>, FreeBSD-scsi <freebsd-scsi@freebsd.org> Subject: Re: mpr(4) SAS3008 Repeated Crashing Message-ID: <BC3018EA-A1F3-4C7C-A179-58553457A938@sarenet.es> In-Reply-To: <56D95266.301@multiplay.co.uk> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BC3018EA-A1F3-4C7C-A179-58553457A938>