Re: nvme INVALID_FIELD in dmesg.boot
- In reply to: Alexander Motin : "Re: nvme INVALID_FIELD in dmesg.boot"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 25 May 2022 16:19:04 UTC
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").