Date: Sun, 29 Apr 2018 15:14:05 +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-8XlFKj25nN@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 Len White <lwhite@nrw.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lwhite@nrw.ca --- Comment #61 from Len White <lwhite@nrw.ca> --- I've recently hit the error nvme0: Missing interrupt on 10.3 and 12.0-curre= nt.=20 I discovered a workaround that may help lead to a proper fix, though I don't know for certain if the Missing interrupt is related to resetting controller message. If I have nvme_load=3D"YES" and nvd_load=3D"YES" in /boot/loader.conf, I get missing interrupt every time, the more the device gets used the more of the messages show up. Each time that message is shown it seems the read/write operation fails as the end result is corruption (AND oddly half the time my intel ix card doesn't work properly when this happens it will spit out ix0: TX(0) desc avail =3D 34, pidx =3D 87, link status stays no carrier) If I load nvme/nvd AFTER the system finishes booting, it behaves normally a= nd doesn't affect ix. So it seems loading nvme/nvd early in the boot process causes some kind of interrupt conflict with other driver(s). --=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-8XlFKj25nN>