From owner-freebsd-scsi@freebsd.org  Mon Dec 11 23:51:53 2017
Return-Path: <owner-freebsd-scsi@freebsd.org>
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 CD31EE80588
 for <freebsd-scsi@mailman.ysv.freebsd.org>;
 Mon, 11 Dec 2017 23:51:53 +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 BA4B780183
 for <freebsd-scsi@FreeBSD.org>; Mon, 11 Dec 2017 23:51:53 +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 vBBNprtL019986
 for <freebsd-scsi@FreeBSD.org>; Mon, 11 Dec 2017 23:51:53 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-scsi@FreeBSD.org
Subject: [Bug 224064] [nvme][hang][resume] nvme_ctrlr_wait_for_ready called
 with desired_val = 0 but cc.en =1
Date: Mon, 11 Dec 2017 23:51:53 +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: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: chuck@tuffli.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-scsi@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-224064-5312-QMbXHKyTIT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224064-5312@https.bugs.freebsd.org/bugzilla/>
References: <bug-224064-5312@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-scsi@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi/>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Dec 2017 23:51:53 -0000

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

--- Comment #7 from chuck@tuffli.net ---
It would be interesting to see what, if any, failure occurs without adding a
specific quirk for your device. So if you have the time and inclination, I'd
vote for experiment #1 to be the D13389 patch without changes and experimen=
t #2
to be the D13389 patch plus an entry in pci_ids for your device with .quirks
set to QUIRK_DELAY_B4_CHK_RDY.

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