Date: Mon, 03 Oct 2022 16:21:09 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262969] NVMe - Resetting controller due to a timeout and possible hot unplug Message-ID: <bug-262969-227-eqdc3uNAAQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262969-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262969-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=3D262969 --- Comment #8 from Timothy Guo <firemeteor@users.sourceforge.net> --- (In reply to Ian Brennan from comment #6) Was that a migration from TrueNAS core to Scale? Did you run into any regression specific to TrueNAS Scale? I heard Scale is less mature than Cor= e. My SW setup used to be stable until I added that NVME disk as an upgrade. I really wish I can avoid any SW migration since the SW setup has been there working just fine for 8+ years with quite a few weird customization -- XEN virtualization, LXC container in dom0 served by TrueNAS core as a XEN guest. XEN virtualization and PCI passthrough could be a factor in this problem bu= t so far I haven't found any evidence yet... My current top suspect is still the APST feature in FreeBSD driver... --=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-262969-227-eqdc3uNAAQ>