Re: I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot
- Reply: Mark Millard via freebsd-current : "Re: I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot"
- In reply to: Mark Millard via freebsd-current : "Re: I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 02 Jul 2021 15:38:42 UTC
On Thu, Jun 24, 2021 at 11:50 PM Mark Millard via freebsd-current <freebsd-current@freebsd.org> wrote: > > I've given up on figuring any useful out for this example. > I've also not had a repeat so far. > > I'm progressing to much more recent commits for the > environment to be based on as well. > > The primary aarch64 system for my access is switching to > be a HoneyComb. The Optane was moved to the HoneyComb. Since the architecture isn't x86, I'm wondering if what you are seeing is related to the changes being proposed in these Differentials: https://reviews.freebsd.org/D30995 https://reviews.freebsd.org/D31002 --chuck