From owner-freebsd-bugs@freebsd.org  Sat Jan 21 03:22:33 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 1AB11CBADC0
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 21 Jan 2017 03:22:33 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 F3DBB1AC2
 for <freebsd-bugs@FreeBSD.org>; Sat, 21 Jan 2017 03:22:32 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0L3MWOF025834
 for <freebsd-bugs@FreeBSD.org>; Sat, 21 Jan 2017 03:22:32 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 211852] Unsafe shutdowns on Intel 750 SSD
Date: Sat, 21 Jan 2017 03:22:33 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: rpokala@panasas.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-211852-8-sagxbA21Av@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211852-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-211852-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jan 2017 03:22:33 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211852

Ravi Pokala <rpokala@panasas.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jimharris@FreeBSD.org

--- Comment #3 from Ravi Pokala <rpokala@panasas.com> ---
As it happens, I also have an Intel 750; dumping it's identify info:

----------------------------------------------------------------
[threepio:dev/base/head] rpokala% sudo nvmecontrol identify -x nvme0
000: 80868086 51435643 32323435 304a3030 41303034 20204e47 45544e49 5353204=
c=20
020: 44455044 3034574d 20344730 20202020 20202020 20202020 20202020 2020202=
0=20
040: 31564538 31373130 5cd2e400 00000500 00000000 00000000 00000000 0000000=
0=20
060: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
080: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
0a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
0c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
0e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
100: 03030006 003f0202 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
120: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
140: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
160: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
180: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
1a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
1c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
1e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
200: 00004466 00000001 00000006 00000007 00000000 00000000 00000000 0000000=
0=20
220: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
240: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
260: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
280: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
2a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000=
0=20
----------------------------------------------------------------

RTD3E is in bytes 91:88, which are offsets 0x58-0x5B in hex, which are zero=
ed
out. So, even if the code was updated to look at and honor RTD3E, it wouldn=
't
help in this case. :-(

Perhaps we should make the SHN wait time configurable? Default to 5 seconds,
overridden by RTD3E if present, overridden by per-device sysctl if set?

--=20
You are receiving this mail because:
You are the assignee for the bug.=