From owner-freebsd-bugs@freebsd.org Fri Mar 17 20:18:48 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 27062D0FCC1 for ; Fri, 17 Mar 2017 20:18: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 1705A1A5E for ; Fri, 17 Mar 2017 20:18: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 v2HKIl2A003520 for ; Fri, 17 Mar 2017 20:18:47 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: Fri, 17 Mar 2017 20:18:47 +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: imp@FreeBSD.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: Fri, 17 Mar 2017 20:18:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211713 --- Comment #24 from Warner Losh --- Gen2 PCIe is limited to 2GB/s for that setup. That's your problem. and like= ly an indicator of the solution... When you say 'under ubuntu' is that on the same physical hardware or a different system? If it is just a reboot between the two performance profil= es, that tells me one thing. If it is in a physically separate box, that tells = me something else. At work we have some drives that are defective (bad resistors that need to = be swapped out) because they can't keep the link established at x4 PCIe3 speed= s. Either they fall back to x1 PCIe3 speeds or x2 and/or PCIe2 speeds. And when they do, they aren't super reliable, in addition to being slow. FreeBSD currently does a poor job of dealing with PCIe errors, so links can= get into crazy states where they perform horribly. Maybe Linux is better able to reset the links on errors. If so, then that's up the alley of some uncommit= ted AER / Link retrain code I've been working on. --=20 You are receiving this mail because: You are the assignee for the bug.=