From owner-freebsd-scsi@freebsd.org Thu Mar 3 10:26:32 2016 Return-Path: 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 39593A93B9C for ; Thu, 3 Mar 2016 10:26:32 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu01176a.smtpx.saremail.com (cu01176a.smtpx.saremail.com [195.16.150.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 F01FB987 for ; Thu, 3 Mar 2016 10:26:31 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.96] (izaro.sarenet.es [192.148.167.11]) by proxypop03.sare.net (Postfix) with ESMTPSA id BEAF29DE159; Thu, 3 Mar 2016 11:26:27 +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 In-Reply-To: <56D805FD.50500@multiplay.co.uk> Date: Thu, 3 Mar 2016 11:26:27 +0100 Cc: Scott Long , FreeBSD-scsi Content-Transfer-Encoding: quoted-printable Message-Id: References: <56D5FDB8.8040402@freebsd.org> <56D612FA.6090909@multiplay.co.uk> <56D805FD.50500@multiplay.co.uk> To: Steven Hartland X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2016 10:26:32 -0000 > On 03 Mar 2016, at 10:38, Steven Hartland = wrote: >=20 > We've seen HW issues before where the first thing to start triggering = the problem was TRIM requests, it seems like its an afterthought in most = FW's unfortunately, so one of the first things to go bad. I'm not saying = this is you issue, but its something to keep in mind. Thanks :) Not trim related, it seems. I=E2=80=99ve ran the tests with = kern.cam.X.delete_method set to DISABLE and I still see errors: In paranormal cases like this it would be awesome to have access to a = logic analyzer=E2=80=A6 I keep dreaming of course :) Mar 3 11:12:53 clientes-ssd8 kernel: (noperiph:mpr0:0:4294967295:0): = SMID 2 Aborting command 0xfffffe0000c7cab0 Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): READ(10). CDB: = 28 00 26 d7 d0 98 00 00 20 00 length 16384 SMID 322 terminated ioc 804b = scsi 0 state c xfer 0 Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): READ(10). CDB: = 28 00 26 d7 d0 b8 00 00 18 00 length 12288 SMID 217 terminated ioc 804b = scsi 0 state c xfer 0 Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): SYNCHRONIZE = CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00 length 0 SMID 205 = terminated ioc 804b scsi 0 sta(da2:mpr0:0:26:0): READ(10). CDB: 28 00 26 = d7 d0 18 00 00 78 00=20 Mar 3 11:12:54 clientes-ssd8 kernel: te c xfer 0 Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): CAM status: = Command timeout Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): Retrying = command Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): SYNCHRONIZE = CACHE(10). CDB: 35 00 00 00 00 00 00 00 00 00=20 Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): CAM status: = SCSI Status Error Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): SCSI status: = Check Condition Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): SCSI sense: = UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred) Mar 3 11:12:54 clientes-ssd8 kernel: (da2:mpr0:0:26:0): Retrying = command (per sense data) Borja.