Date: Sun, 15 Oct 2023 09:53:45 -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: <CANCZdfr_OEZuBxcii1h7EW76QA3%2BgWVfMNe=M-=P5FzF3%2BsM8A@mail.gmail.com> In-Reply-To: <ab4f7711-7daf-4a29-8de4-565c5e0b1f48@app.fastmail.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> <ab4f7711-7daf-4a29-8de4-565c5e0b1f48@app.fastmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, Oct 15, 2023, 9:47 AM void <void@f-m.fm> wrote: > 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. > The one with the uboot traceback? I can't help you there. The report is confusing. I don't know the error / problem being reported to even know what to look at. Or is it a different thing? I'm so confused at this point. I also think we need to recreate it on as a!clean system as possible. Weird problems in the boot chain prior to loader.efi, I have little interest in and no time to look at... 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:47 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">On Sun, 15 Oct 2023, at 15:35, Warner Losh wrote:<br> <br> > I've fixed all known nvme issues in current that aren't caused by other <br> > parts of the system. If it isn't a very recent 15 or 14, then there <br> > are known issues and you'll need to try those first.<br> <br> The problem manifested with a source upgrade on the 30th September. <br> <br> > On arm it could be a lot of things. I keep seeing problems in other <br> > area that are hard to track down.... without the systems in hand and <br> > time to look at complex problems it can take a while to track down.<br> ><br> > I'll need a simple reproducer to look at things... <br> <br> If you can tell me what to do, i'm happy to test.<br> <br> Additionally, I can provide a connected instance to you for destructive <br> testing on arm64. It would take me about 24hrs to set up as I'd<br> need to backup the disk. Let me know if you need it.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">The one with the uboot traceback? I can't help you there. The report is confusing. I don't know the error / problem being reported to even know what to look at. Or is it a different thing? I'm so confused at this point. I also think we need to recreate it on as a!clean system as possible. Weird problems in the boot chain prior to loader.efi, I have little interest in and no time to look at...</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?CANCZdfr_OEZuBxcii1h7EW76QA3%2BgWVfMNe=M-=P5FzF3%2BsM8A>