Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Mar 2016 11:26:27 +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:  <F9B68610-12C6-4D32-88CA-A34A185F9AD1@sarenet.es>
In-Reply-To: <56D805FD.50500@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>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 03 Mar 2016, at 10:38, Steven Hartland <killing@multiplay.co.uk> =
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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F9B68610-12C6-4D32-88CA-A34A185F9AD1>