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
On Sun, Oct 15, 2023, 9:47 AM void 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
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 Sun, Oct 15, 2023, 9:28 AM void 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
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
