Date: Wed, 25 May 2022 09:19:04 -0700 From: Chuck Tuffli <chuck@freebsd.org> To: Alexander Motin <mav@freebsd.org> Cc: Matteo Riondato <matteo@freebsd.org>, FreeBSD-Current <freebsd-current@freebsd.org>, Jim Harris <jimharris@freebsd.org> Subject: Re: nvme INVALID_FIELD in dmesg.boot Message-ID: <CAKAYmMKHwN5YaMS3-_%2BFZVpdTaWWbQetT4x5gkCBLqLmG6Mx6A@mail.gmail.com> In-Reply-To: <d8462935-2874-2e5c-a7aa-d5352bd0a3c2@FreeBSD.org> References: <20220525122529.t2kwfg2q65dfiyyt@host-ubertino-mac-88e9fe7361f5.eduroam.ssid.10net.amherst.edu> <d8462935-2874-2e5c-a7aa-d5352bd0a3c2@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 25, 2022 at 6:59 AM Alexander Motin <mav@freebsd.org> wrote: ... > > nvme0: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:0000000b cdw11:0000031f > > nvme0: INVALID_FIELD (00/02) sqid:0 cid:15 cdw0:0 ... > Those messages mean that driver tried to enable certain types of > asynchronous events, but probably the hardware does not support some of Du-oh! I read the 'b' in 0000000b as 'binary'. Alexander and Warner are correct that this is from setting an AEN, and I was wrong about CDW10 causing the error. FWIW, "CDW" in NVMe-land is shorthand for Command DWord as NVMe commands are composed of 32-bit fields (ancient Intel/Microsoft "double words").
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKAYmMKHwN5YaMS3-_%2BFZVpdTaWWbQetT4x5gkCBLqLmG6Mx6A>