Date: Sun, 15 Oct 2023 15:46:26 +0000 From: void <void@f-m.fm> To: freebsd-current <freebsd-current@freebsd.org> Subject: Re: nvme timeout issues with hardware and bhyve vm's Message-ID: <ab4f7711-7daf-4a29-8de4-565c5e0b1f48@app.fastmail.com> In-Reply-To: <CANCZdfr36gK3jUqvx20K%2Bgo28i%2BH_s-FQeC3o0gj339JkVXv-w@mail.gmail.com> References: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> <2d93d966-dc4e-4448-a182-95eb8e2e13e7@app.fastmail.com> <CANCZdfr36gK3jUqvx20K%2Bgo28i%2BH_s-FQeC3o0gj339JkVXv-w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 15 Oct 2023, at 15:35, Warner Losh wrote: > 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. The problem manifested with a source upgrade on the 30th September. > 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... If you can tell me what to do, i'm happy to test. Additionally, I can provide a connected instance to you for destructive testing on arm64. It would take me about 24hrs to set up as I'd need to backup the disk. Let me know if you need it. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ab4f7711-7daf-4a29-8de4-565c5e0b1f48>