From owner-freebsd-bugs@freebsd.org Sun Apr 29 15:14:15 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8802BFAFBE7 for ; Sun, 29 Apr 2018 15:14:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 07CCD682E7 for ; Sun, 29 Apr 2018 15:14:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B2DAAFAFBE4; Sun, 29 Apr 2018 15:14:14 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A154BFAFBE3 for ; Sun, 29 Apr 2018 15:14:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 409DF682E4 for ; Sun, 29 Apr 2018 15:14:14 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6B33F1C165 for ; Sun, 29 Apr 2018 15:14:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3TFEDRt080192 for ; Sun, 29 Apr 2018 15:14:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3TFEDSs080181 for bugs@FreeBSD.org; Sun, 29 Apr 2018 15:14:13 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 211713] NVME controller failure: resetting (Samsung SM961 SSD Drives) Date: Sun, 29 Apr 2018 15:14:05 +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: needs-qa X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: lwhite@nrw.ca X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: 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.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 15:14:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211713 Len White changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lwhite@nrw.ca --- Comment #61 from Len White --- I've recently hit the error nvme0: Missing interrupt on 10.3 and 12.0-curre= nt.=20 I discovered a workaround that may help lead to a proper fix, though I don't know for certain if the Missing interrupt is related to resetting controller message. If I have nvme_load=3D"YES" and nvd_load=3D"YES" in /boot/loader.conf, I get missing interrupt every time, the more the device gets used the more of the messages show up. Each time that message is shown it seems the read/write operation fails as the end result is corruption (AND oddly half the time my intel ix card doesn't work properly when this happens it will spit out ix0: TX(0) desc avail =3D 34, pidx =3D 87, link status stays no carrier) If I load nvme/nvd AFTER the system finishes booting, it behaves normally a= nd doesn't affect ix. So it seems loading nvme/nvd early in the boot process causes some kind of interrupt conflict with other driver(s). --=20 You are receiving this mail because: You are the assignee for the bug.=