From owner-freebsd-scsi@freebsd.org Fri Oct 20 18:02:35 2017 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 B37E0E3C364 for ; Fri, 20 Oct 2017 18:02:35 +0000 (UTC) (envelope-from shiva.bhanujan@quorum.com) Received: from asp.reflexion.net (outbound-mail-211-161.reflexion.net [208.70.211.161]) (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 5A7D8E3A for ; Fri, 20 Oct 2017 18:02:35 +0000 (UTC) (envelope-from shiva.bhanujan@quorum.com) Received: (qmail 5659 invoked from network); 20 Oct 2017 17:55:54 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 20 Oct 2017 17:55:53 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Fri, 20 Oct 2017 13:55:53 -0400 (EDT) Received: (qmail 19031 invoked from network); 20 Oct 2017 17:55:53 -0000 Received: from unknown (HELO mail.quorum.net) (64.74.133.216) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Oct 2017 17:55:53 -0000 Received: from QLEXC01.Quorum.local ([fe80::edb6:63d5:778f:2f0e]) by QLEXC01.Quorum.local ([fe80::edb6:63d5:778f:2f0e%14]) with mapi id 14.03.0351.000; Fri, 20 Oct 2017 10:55:52 -0700 From: Shiva Bhanujan To: Ken Merry CC: Steven Hartland , "freebsd-scsi@freebsd.org" Subject: RE: FreeBSD 10.3/11.0 SCSI errors with Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 Thread-Topic: FreeBSD 10.3/11.0 SCSI errors with Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 Thread-Index: AQHTQ80AKMPHqs1A+0yLHlbMiv8g5KLiNr7zgATQ/oCAADv2uIAAihwAgAA6+IKAANcq6YAAAGPJgANMRoCAAABZAP//kIxpgACCBAD//7I104AAjO6AgABG8C+AAIlaAP//wmiN Date: Fri, 20 Oct 2017 17:55:51 +0000 Message-ID: <3A5A10BE32AC9E45B4A22F89FC90EC0701C36667DC@QLEXC01.Quorum.local> References: <3A5A10BE32AC9E45B4A22F89FC90EC0701C3665D5D@QLEXC01.Quorum.local> <3A5A10BE32AC9E45B4A22F89FC90EC0701C3665E8B@QLEXC01.Quorum.local> <20171016144231.GA94858@mithlond.kdm.org> <3A5A10BE32AC9E45B4A22F89FC90EC0701C366610E@QLEXC01.Quorum.local> <20171017023126.GA6559@mithlond.kdm.org> <3A5A10BE32AC9E45B4A22F89FC90EC0701C3666143@QLEXC01.Quorum.local> <3A5A10BE32AC9E45B4A22F89FC90EC0701C3666345@QLEXC01.Quorum.local> <3A5A10BE32AC9E45B4A22F89FC90EC0701C3666352@QLEXC01.Quorum.local> <3E746990-8C6D-4CA1-BD79-B5566CFB07F4@freebsd.org> <32C157CE-A122-435F-8430-9531BEEB5914@freebsd.org> <3A5A10BE32AC9E45B4A22F89FC90EC0701C3666647@QLEXC01.Quorum.local> <3A5A10BE32AC9E45B4A22F89FC90EC0701C36666F5@QLEXC01.Quorum.local> <96BAD947-4AB0-4EAC-9DA8-4B1F10253287@freebsd.org> <3A5A10BE32AC9E45B4A22F89FC90EC0701C366674D@QLEXC01.Quorum.local>, <95A66B26-548C-4BF5-9527-EE30F9C01D42@freebsd.org> In-Reply-To: <95A66B26-548C-4BF5-9527-EE30F9C01D42@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.20.7.63] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 18:02:35 -0000 Thanks for the patch. I applied the patch on FreeBSD 10.3 and it has = addressed the issue. I've added the following to /boot/loader.conf. hw.mpr.disable_eedp=3D=221=22 ev.mpr.0.disable_eedp=3D=221=22 I'm going to apply the patch in FreeBSD 11.1 also, just to make sure that = works. Is this going to be checked into stable/10 and/or stable/11? From: Ken Merry =5Bken=40freebsd.org=5D Sent: Friday, October 20, 2017 7:34 AM To: Shiva Bhanujan Cc: Steven Hartland; freebsd-scsi=40freebsd.org Subject: Re: FreeBSD 10.3/11.0 SCSI errors with Symbios Logic SAS3008 = PCI-Express Fusion-MPT SAS-3 Ok. Yes, for =232, in theory we can disable EEDP / protection information = in the mpr(4) driver and if DPICZ is set, the drive won=E2=80=99t require = setting protection information on read and write commands. That should let you access the disks normally. That said, I=E2=80=99ve never played with protection information before, = so I don=E2=80=99t know for sure. I have a drive that supports it and = I=E2=80=99m formatting it now to turn on type 2 protection I may be able = to debug things once I get that done. In the mean time, I=E2=80=99ve attached a patch against the stable/10 = version of the mpr(4) driver. Apply this patch, and rebuild and reinstall = your kernel. Then you=E2=80=99ll be able to disable EEDP in the driver = three different ways: 1. Set hw.mpr.disable_eedp=3D1 in /boot/loader.conf. That will disable = EEDP / Protection Information for all mpr instances. 2. Set dev.mpr.0.disable_eedp=3D1 in /boot/loader.conf. That will disable = EEDP for mpr0. 3. sysctl dev.mpr.0.disable_eedp=3D1 That will disable EEDP on the fly for = mpr0. Let me know what happens. Ken =E2=80=94=20 Ken Merry ken=40FreeBSD.ORG