Date: Sun, 07 Jul 2019 21:15:21 +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-3oColfWJ1o@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 --- Comment #81 from Terry Kennedy <terry-freebsd@glaver.org> --- My only potential concern with this patch is that in my original testing, I found that the NVMe drive worked on some systems and not others (under Free= BSD; under Linux I could not get it to fail anywhere). Is it possible that we're seeing a difference in the way the BIOS sets things up? If so, is the propo= sed patch the way to go, or should we do further diagnosis to see if we can find what the actual BIOS initialization differences are? OTOH, if nobody else thinks there are issues with the patch, good to go. I'm just concerned about changing this behavior globally as opposed to just on = the NVMe device. --=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-3oColfWJ1o>