From owner-freebsd-bugs@freebsd.org Fri Mar 17 20:47:58 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 54AD3D10D67 for ; Fri, 17 Mar 2017 20:47:58 +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 281881295 for ; Fri, 17 Mar 2017 20:47:58 +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 v2HKlw8P074187 for ; Fri, 17 Mar 2017 20:47:58 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:47:58 +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: Fri, 17 Mar 2017 20:47:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211713 --- Comment #25 from Terry Kennedy --- (In reply to Warner Losh from comment #24) I think there may be multiple bugs all getting lumped into this PR. On my Dell R710 (same exact CPUs, memory modules, and system chipset as the Supermicro X8DTH-iF where I get the hangs) with FreeBSD 10.3-STABLE, I get: (0:4) pool20:/sysprog/terry# dd if=3D/dev/nvd0 of=3D/dev/null bs=3D16m 7631+1 records in 7631+1 records out 128035676160 bytes transferred in 86.524463 secs (1479762738 bytes/sec) (0:5) pool20:/sysprog/terry# dd if=3D/dev/zero of=3D/dev/nvd0 bs=3D16m dd: /dev/nvd0: short write on character device dd: /dev/nvd0: end of device 7632+0 records in 7631+1 records out 128035676160 bytes transferred in 164.568004 secs (778010750 bytes/sec) (1:6) pool20:/sysprog/terry# pciconf -lbace nvme0 nvme0@pci0:5:0:0: class=3D0x010802 card=3D0xa801144d chip=3D0xa804144= d rev=3D0x00 hdr=3D0x00 bar [10] =3D type Memory, range 64, base 0xdf2fc000, size 16384, enab= led cap 01[40] =3D powerspec 3 supports D0 D3 current D0 cap 05[50] =3D MSI supports 32 messages, 64 bit=20 cap 10[70] =3D PCI-Express 2 endpoint max data 256(256) FLR RO NS link = x4(x4) speed 5.0(8.0) ASPM disabled(L1) cap 11[b0] =3D MSI-X supports 33 messages, enabled Table in map 0x10[0x3000], PBA in map 0x10[0x2000] ecap 0001[100] =3D AER 2 0 fatal 0 non-fatal 0 corrected ecap 0003[148] =3D Serial 1 0000000000000000 ecap 0004[158] =3D Power Budgeting 1 ecap 0019[168] =3D PCIe Sec 1 lane errors 0 ecap 0018[188] =3D LTR 1 ecap 001e[190] =3D unknown 1 This is in a PCIe 2 x4 slot, but the write speed matches the SM961 datasheet for the 128GB version - "700MB/Sec sequential write". Sequential read is probably being limited by PCIe 2 speeds, as the datasheet specifies "Up to 3100MB/Sec". These numbers are from "Samsung Rev 1.0, June 2016". I can't p= ost the whole thing as it is marked Company Confidential. On the Supermicro X8DTH-iF where FreeBSD gets the controller resets, Arch L= inux 2016.11.01 reads and writes the SM961 at approximately the same speeds as on the Dell R710, with no resets. --=20 You are receiving this mail because: You are the assignee for the bug.=