Date: Sun, 15 Oct 2023 09:35:18 -0600 From: Warner Losh <imp@bsdimp.com> To: void <void@f-m.fm> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: nvme timeout issues with hardware and bhyve vm's Message-ID: <CANCZdfr36gK3jUqvx20K%2Bgo28i%2BH_s-FQeC3o0gj339JkVXv-w@mail.gmail.com> In-Reply-To: <2d93d966-dc4e-4448-a182-95eb8e2e13e7@app.fastmail.com> References: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> <2d93d966-dc4e-4448-a182-95eb8e2e13e7@app.fastmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, Oct 15, 2023, 9:28 AM void <void@f-m.fm> wrote: > Hi, > > On Fri, 13 Oct 2023, at 03:40, Pete Wright wrote: > > I had similar issues on my workstation as well. Scrubbing the NVMe > > device on my real-hardware workstation hasn't turned up any issues, but > > the system has locked up a handful of times. > > > > Just curious if others have seen the same, or if someone could point me > > in the right direction... > > I've seen similar issues (zpool timeout) in a quite different context > (arm64, usb3-connected disk, not-vm) which i posted about here: > > https://lists.freebsd.org/archives/freebsd-arm/2023-September/003122.html > > Unsure if these have been fixed yet? > I've fixed all known nvme issues in current that aren't caused by other parts of the system. If it isn't a very recent 15 or 14, then there are known issues and you'll need to try those first. On arm it could be a lot of things. I keep seeing problems in other area that are hard to track down.... without the systems in hand and time to look at complex problems it can take a while to track down. I'll need a simple reproducer to look at things... Warner > [-- Attachment #2 --] <div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Oct 15, 2023, 9:28 AM void <<a href="mailto:void@f-m.fm">void@f-m.fm</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br> <br> On Fri, 13 Oct 2023, at 03:40, Pete Wright wrote:<br> > I had similar issues on my workstation as well. Scrubbing the NVMe <br> > device on my real-hardware workstation hasn't turned up any issues, but <br> > the system has locked up a handful of times.<br> ><br> > Just curious if others have seen the same, or if someone could point me <br> > in the right direction...<br> <br> I've seen similar issues (zpool timeout) in a quite different context <br> (arm64, usb3-connected disk, not-vm) which i posted about here:<br> <br> <a href="https://lists.freebsd.org/archives/freebsd-arm/2023-September/003122.html" rel="noreferrer noreferrer" target="_blank">https://lists.freebsd.org/archives/freebsd-arm/2023-September/003122.html</a><br>; <br> Unsure if these have been fixed yet?<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I've fixed all known nvme issues in current that aren't caused by other parts of the system. If it isn't a very recent 15 or 14, then there are known issues and you'll need to try those first.</div><div dir="auto"><br></div><div dir="auto">On arm it could be a lot of things. I keep seeing problems in other area that are hard to track down.... without the systems in hand and time to look at complex problems it can take a while to track down.</div><div dir="auto"><br></div><div dir="auto">I'll need a simple reproducer to look at things... </div><div dir="auto"><br></div><div dir="auto">Warner </div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> </blockquote></div></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfr36gK3jUqvx20K%2Bgo28i%2BH_s-FQeC3o0gj339JkVXv-w>