From owner-freebsd-bugs@freebsd.org Mon Nov 28 01:22:52 2016
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 05D98C5887B
for <freebsd-bugs@mailman.ysv.freebsd.org>;
Mon, 28 Nov 2016 01:22:52 +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 E71DC3B16
for <freebsd-bugs@FreeBSD.org>; Mon, 28 Nov 2016 01:22:51 +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 uAS1MpGp001032
for <freebsd-bugs@FreeBSD.org>; Mon, 28 Nov 2016 01:22:51 GMT
(envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 211713] NVME controller failure: resetting
Date: Mon, 28 Nov 2016 01:22:51 +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 Only Me
X-Bugzilla-Who: terry-freebsd@glaver.org
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-211713-8-LArNuL89DX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211713-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-211713-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: Mon, 28 Nov 2016 01:22:52 -0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211713
Terry Kennedy <terry-freebsd@glaver.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |terry-freebsd@glaver.org
--- Comment #5 from Terry Kennedy <terry-freebsd@glaver.org> ---
I have the same problem on 10-STABLE (r309209) with a 128GB SM961 and can a=
lso
reproduce it on CURRENT (20161117 snapshot). Even attempting to read the de=
vice
with dd causes the error:
(0:21) pool13:/sysprog/terry# dd if=3D/dev/nvme0ns1 of=3D/dev/null count=3D1
nvme0: resetting controller
nvme0: aborting outstanding i/o
nvme0: READ sqid:8 cid:127 nsid:1 lba:3 len:1
nvme0: ABORTED - BY REQUEST (00/07) sqid:8 cid:127 cdw0:0
nvmecontrol reports that the drive has never experienced an error, even aft=
er
the above:
(0:30) pool13:/sysprog/terry# nvmecontrol logpage -p 1 nvme0
Error Information Log
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
No error entries found
smartctl similarly reports no problems.
Booting Arch Linux 2016.11.01 lets me read and write to the drive with no
problems, so I don't think this is a hardware problem.
I have the module in a dedicated test system and can provide a https:// rem=
ote
console to the developer(s) if it would help to pin down the problem. Let me
know if you'd like any further information.
--=20
You are receiving this mail because:
You are the assignee for the bug.=