Date: Mon, 30 May 2022 14:14:03 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 264172] nvme(4): PM9A1 NVMe Samsung 512GB no longer available with 13.1-RELEASE (was working with 13.0) Message-ID: <bug-264172-227-p5OLony0vr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264172-227@https.bugs.freebsd.org/bugzilla/> References: <bug-264172-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=3D264172 --- Comment #9 from Warner Losh <imp@FreeBSD.org> --- Does a -current snapshot have the same issue? vmm is this "thing" Intel invented. It's designed to be raid without the hassles, but it falls well short of that design goal. Basically, the nvme drives need to be accessed via the ACHI controller, and vmm.c provides that glue in what's supposed to be a seamless way. If it works with a -current snapshot, then vmm isn't broken there and we're missing some key bit of code in 13.1. If it is broken there, then that's a whole different problem to solve (a currently unknown issue with vmm). I disabled VMM on my laptop years ago, and am reluctant to re-enable it since I'll have to back/restore windows in the process, which was the better part= of a day for me the last time I fought with it... Though if I do that, I can upgrade my BIOS and maybe run Windows 11 (if only I had a day to burn on this...) --=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-264172-227-p5OLony0vr>