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>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000001a6abe0607c30a7a Content-Type: text/plain; charset="UTF-8" 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 > --0000000000001a6abe0607c30a7a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" = class=3D"gmail_attr">On Sun, Oct 15, 2023, 9:28 AM void <<a href=3D"mail= to:void@f-m.fm">void@f-m.fm</a>> wrote:<br></div><blockquote class=3D"gm= ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le= ft: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.=C2=A0 Scrubbing the NV= Me <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 m= e <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=3D"https://lists.freebsd.org/archives/freebsd-arm/2023-September/00= 3122.html" rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.fr= eebsd.org/archives/freebsd-arm/2023-September/003122.html</a><br> <br> Unsure if these have been fixed yet?<br></blockquote></div></div><div dir= =3D"auto"><br></div><div dir=3D"auto">I've fixed all known nvme issues = in current that aren't caused by other parts of the system. If it isn&#= 39;t a very recent 15 or 14,=C2=A0 then there are known issues and you'= ll need to try those first.</div><div dir=3D"auto"><br></div><div dir=3D"au= to">On arm it could be a lot of things. I keep seeing problems in other are= a that are hard to track down.... without the systems in hand and time to l= ook at complex problems it can take a while to track down.</div><div dir=3D= "auto"><br></div><div dir=3D"auto">I'll need a simple reproducer to loo= k at things...=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">War= ner=C2=A0</div><div dir=3D"auto"><div class=3D"gmail_quote"><blockquote cla= ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa= dding-left:1ex"> </blockquote></div></div></div> --0000000000001a6abe0607c30a7a--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfr36gK3jUqvx20K%2Bgo28i%2BH_s-FQeC3o0gj339JkVXv-w>