Date: Mon, 28 Nov 2016 01:22:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211713] NVME controller failure: resetting Message-ID: <bug-211713-8-LArNuL89DX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211713-8@https.bugs.freebsd.org/bugzilla/> References: <bug-211713-8@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713 Terry Kennedy <terry-freebsd@glaver.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |terry-freebsd@glaver.org --- Comment #5 from Terry Kennedy <terry-freebsd@glaver.org> --- I have the same problem on 10-STABLE (r309209) with a 128GB SM961 and can also reproduce it on CURRENT (20161117 snapshot). Even attempting to read the device with dd causes the error: (0:21) pool13:/sysprog/terry# dd if=/dev/nvme0ns1 of=/dev/null count=1 nvme0: resetting controller nvme0: aborting outstanding i/o nvme0: READ sqid:8 cid:127 nsid:1 lba:3 len:1 nvme0: ABORTED - BY REQUEST (00/07) sqid:8 cid:127 cdw0:0 nvmecontrol reports that the drive has never experienced an error, even after the above: (0:30) pool13:/sysprog/terry# nvmecontrol logpage -p 1 nvme0 Error Information Log ===================== No error entries found smartctl similarly reports no problems. Booting Arch Linux 2016.11.01 lets me read and write to the drive with no problems, so I don't think this is a hardware problem. I have the module in a dedicated test system and can provide a https:// remote console to the developer(s) if it would help to pin down the problem. Let me know if you'd like any further information. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211713-8-LArNuL89DX>