From owner-freebsd-bugs@freebsd.org Wed Mar 15 06:47:39 2017 Return-Path: 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 A5D6DD0D23A for ; Wed, 15 Mar 2017 06:47: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 mx1.freebsd.org (Postfix) with ESMTPS id 95B2A1E1C for ; Wed, 15 Mar 2017 06:47:39 +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 v2F6ldSf091195 for ; Wed, 15 Mar 2017 06:47:39 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: Wed, 15 Mar 2017 06:47:39 +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: terry-freebsd@glaver.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: 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.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2017 06:47:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211713 --- Comment #21 from Terry Kennedy --- (In reply to Warner Losh from comment #19) It is a MZVPW128HEGM-00000 which is a SM961. This has happened in multiple systems (identical hardware configs - see below) which otherwise are operat= ing flawlessly. In previous correspondence with jimharris@, he had me try setting hw.nvme.per_cpu_io_queues=3D0 which concealed the problem but resulted in a= bysmal I/O performance (as expected). He also had me set some debug loader tunables and post the results. Those are at https://www.glaver.org/transient/nvme I just moved the card (SM961 on generic PCIe slot adapter) to a Dell PowerE= dge R710. It had been in a Supermicro X8DTH-iF. It works fine in the R710, even= on 10.3-STABLE. Both of those systems are as similar as I could make them - bo= th use the Intel 5520 chipset, both have 2 * X5680 CPU, both have 48GB of RAM (same part number in both systems). So it seems (at least in my case) to be related to the system hardware. I can try ordering some other M.2 NVMe module to see if this issue is speci= fic to the SM961, or if it is a problem with any NVMe on the X8DTH-iF board. --=20 You are receiving this mail because: You are the assignee for the bug.=