Date: Sun, 15 Oct 2023 16:05:57 +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: <43001417-6398-4f9c-bbaf-1ff89782fdec@app.fastmail.com> In-Reply-To: <CANCZdfr_OEZuBxcii1h7EW76QA3%2BgWVfMNe=M-=P5FzF3%2BsM8A@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> <ab4f7711-7daf-4a29-8de4-565c5e0b1f48@app.fastmail.com> <CANCZdfr_OEZuBxcii1h7EW76QA3%2BgWVfMNe=M-=P5FzF3%2BsM8A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 15 Oct 2023, at 15:53, Warner Losh wrote: > 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... The problem being reported on the 30th Sept is a panic on booting zroot because the disk couldn't be found by the loader, presumably because usb3 needed time to settle, because making it wait a while resulted in a bootable system. But all the waiting does is workaround. I don't know how to fix it permanently. The problem gets to (i guess it's called stage1 boot) where i can select what kernel to boot. At that point, i thought u-boot had completed. The reason I'm mentioning this in this thread is because the OP is reporting an issue looking on the face of it very similar to the one I saw, and i thought mentioning this here might be helpful.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43001417-6398-4f9c-bbaf-1ff89782fdec>