Date: Wed, 28 Nov 2018 00:37:31 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 211713] NVME controller failure: resetting (Samsung SM961 SSD Drives) Message-ID: <bug-211713-227-laufqXY6nu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211713-227@https.bugs.freebsd.org/bugzilla/> References: <bug-211713-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211713 Wolf Noble <freebsd@wolfspaw.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd@wolfspaw.com --- Comment #69 from Wolf Noble <freebsd@wolfspaw.com> --- I can confirm this bug rears it head on a dell r510 running freenas11.2 (wh= ich follows freebsd11.2)=20=20=20=20 if I use a synology m2d18 https://www.synology.com/en-us/products/M2D18 du= al NVME pci card. I cannot get diskinfo to run cleanly without the target goin= g to lunch. Setting hw.nvme.enable_aborts=3D1 via a loader.conf tunable (and rebooting) had no impact in my case. disabling or enabling hyperthreading does not seem to impact this hang, although having hyperthreading enabled seems to prevent MSIX from being use= d. if I take the nvme devices out of the synology dual card and put them into a single nvme->pci adapter, I do not (yet) seem to have the problem. happy to provide whatever details might be useful in making progress, but figured that just the additional info might be sufficiently useful without superfluous noise. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211713-227-laufqXY6nu>