From owner-freebsd-bugs@freebsd.org  Sat Mar 18 19:30:06 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 13DB3D1256B
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 18 Mar 2017 19:30:06 +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 F26F71BAD
 for <freebsd-bugs@FreeBSD.org>; Sat, 18 Mar 2017 19:30:05 +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 v2IJU3Us052689
 for <freebsd-bugs@FreeBSD.org>; Sat, 18 Mar 2017 19:30:05 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: Sat, 18 Mar 2017 19:30:04 +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: imp@FreeBSD.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: 
Message-ID: <bug-211713-8-NQHRm9gGKK@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: Sat, 18 Mar 2017 19:30:06 -0000

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

--- Comment #28 from Warner Losh <imp@FreeBSD.org> ---
OK. It isn't the SM961 generally. I have one in a NUC6 on my desk now (it
arrived last night). With 5 dd's reading it, I can get 2.5GB/s. More dd's d=
on't
help. Data sheet says up to 3.1GB/s. But I'm seeing no errors with my card,
though it has AER reporting. I was able to newfs the 256GB version w/o issu=
e.

I suspect, but cannot prove, this may be a signal issue causing errors. Lin=
ux
seems to cope better maybe? Or maybe it knows to push it less hard? Not sur=
e. I
need to polish off the AER code I've written to monitor other devices I hav=
e.

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