From owner-freebsd-bugs@freebsd.org  Sun Dec 18 16:02:48 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 E8E08C87CD0
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun, 18 Dec 2016 16:02:48 +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 D61141E82
 for <freebsd-bugs@FreeBSD.org>; Sun, 18 Dec 2016 16:02:48 +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 uBIG2mlJ071134
 for <freebsd-bugs@FreeBSD.org>; Sun, 18 Dec 2016 16:02:48 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: Sun, 18 Dec 2016 16:02:49 +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: robin.randhawa@arm.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-211713-8-bc5mjqzGn9@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: Sun, 18 Dec 2016 16:02:49 -0000

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

Robin Randhawa <robin.randhawa@arm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |robin.randhawa@arm.com

--- Comment #6 from Robin Randhawa <robin.randhawa@arm.com> ---
Hi all.

I have a similar issue. My hardware is a Lenovo Thinkpad P50 with a 512GB n=
vme
SSD running current (synced yesterday) with a custom kernel configuration t=
hat
differs from GENERIC only in that VESA is disabled (nvidia issues while
resuming from ACPI S3 if not).

$ nvcontrol devlist
 nvme0: SAMSUNG MZVKV512HAJH-000L1
    nvme0ns1 (488386MB)

The particular manifestation I see is on resume when disk access seems to s=
tall
for 5-10 seconds. The relevant messages in the kernel log buffer are a scary
stream of:

nvme0: READ sqid:6 cid:124 nsid:1 lba:697441256 len:8
nvme0: ABORTED - BY REQUEST (00/07) sqid:6 cid:124 cdw0:0
nvme0: aborting outstanding i/o
nvme0: READ sqid:8 cid:109 nsid:1 lba:399615616 len:40
nvme0: ABORTED - BY REQUEST (00/07) sqid:8 cid:109 cdw0:0

Please let me now if you need any more specifics. Thanks.

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