[Bug 211713] NVME controller failure: resetting
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Nov 28 01:22:52 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
Terry Kennedy <terry-freebsd at glaver.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |terry-freebsd at glaver.org
--- Comment #5 from Terry Kennedy <terry-freebsd at 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.
More information about the freebsd-bugs
mailing list