From owner-freebsd-bugs@freebsd.org Wed Nov 28 00:37:40 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 5E02B11414F8 for ; Wed, 28 Nov 2018 00:37:40 +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 EA80F76A29 for ; Wed, 28 Nov 2018 00:37:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AD91A11414F5; Wed, 28 Nov 2018 00:37:39 +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 9BD2C11414F3 for ; Wed, 28 Nov 2018 00:37:39 +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.3 with cipher TLS_AES_256_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 3A85F76A25 for ; Wed, 28 Nov 2018 00:37:39 +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 53A98F8B4 for ; Wed, 28 Nov 2018 00:37:38 +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 wAS0bc9X043476 for ; Wed, 28 Nov 2018 00:37:38 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wAS0bc72043475 for bugs@FreeBSD.org; Wed, 28 Nov 2018 00:37:38 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: Wed, 28 Nov 2018 00:37:31 +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: freebsd@wolfspaw.com 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-Rspamd-Queue-Id: EA80F76A29 X-Spamd-Result: default: False [1.77 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_SPAM_LONG(0.62)[0.618,0]; NEURAL_SPAM_MEDIUM(0.71)[0.707,0]; ASN(0.00)[asn:10310, ipnet:2001:1900:2254::/48, country:US]; NEURAL_SPAM_SHORT(0.45)[0.447,0] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2018 00:37:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211713 Wolf Noble changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd@wolfspaw.com --- Comment #69 from Wolf Noble --- I can confirm this bug rears it head on a dell r510 running freenas11.2 (wh= ich follows freebsd11.2)=20=20=20=20 if I use a synology m2d18 https://www.synology.com/en-us/products/M2D18 du= al NVME pci card. I cannot get diskinfo to run cleanly without the target goin= g to lunch. Setting hw.nvme.enable_aborts=3D1 via a loader.conf tunable (and rebooting) had no impact in my case. disabling or enabling hyperthreading does not seem to impact this hang, although having hyperthreading enabled seems to prevent MSIX from being use= d. if I take the nvme devices out of the synology dual card and put them into a single nvme->pci adapter, I do not (yet) seem to have the problem. happy to provide whatever details might be useful in making progress, but figured that just the additional info might be sufficiently useful without superfluous noise. --=20 You are receiving this mail because: You are the assignee for the bug.=