Date: Wed, 25 May 2022 10:32:05 -0400 From: Matteo Riondato <matteo@FreeBSD.org> To: Alexander Motin <mav@FreeBSD.org> Cc: freebsd-current@freebsd.org, Jim Harris <jimharris@freebsd.org> Subject: Re: nvme INVALID_FIELD in dmesg.boot Message-ID: <892F7305-97D6-4D78-B1E7-3BEC3809DD75@FreeBSD.org> 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
--Apple-Mail=_BE11DF7B-1C71-4899-8149-2E281E0E4131 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 25, 2022, at 9:58 AM, Alexander Motin <mav@FreeBSD.org> wrote: >=20 > On 25.05.2022 08:25, Matteo Riondato wrote: >> My dmesg.boot contains the following entries containing = "INVALID_FIELD" about nvme (I use nda(4) for my nvme disks, with = hw.nvme.use_nvd=3D0 in loader.conf): >> trismegistus ~ % grep -e 'nvme[0-9]\?' /var/run/dmesg.boot >> nvme0: <Intel DC PC4500> mem 0xb8610000-0xb8613fff irq 40 at device = 0.0 numa-domain 0 on pci7 >> nvme1: <Intel DC PC4500> mem 0xb8510000-0xb8513fff irq 47 at device = 0.0 numa-domain 0 on pci8 >> nvme2: <Intel DC PC4500> mem 0xc5e10000-0xc5e13fff irq 48 at device = 0.0 numa-domain 0 on pci10 >> nvme3: <Intel DC PC4500> mem 0xc5d10000-0xc5d13fff irq 55 at device = 0.0 numa-domain 0 on pci11 >> 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 >> nvme1: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:0000000b = cdw11:0000031f >> nvme1: INVALID_FIELD (00/02) sqid:0 cid:15 cdw0:0 >> nvme2: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:0000000b = cdw11:0000031f >> nvme2: INVALID_FIELD (00/02) sqid:0 cid:15 cdw0:0 >> nvme3: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:0000000b = cdw11:0000031f >> nvme3: INVALID_FIELD (00/02) sqid:0 cid:15 cdw0:0 >> nda0 at nvme0 bus 0 scbus16 target 0 lun 1 >> nda0: nvme version 1.2 x4 (max x4) lanes PCIe Gen3 (max Gen3) link >> nda1 at nvme1 bus 0 scbus17 target 0 lun 1 >> nda1: nvme version 1.2 x4 (max x4) lanes PCIe Gen3 (max Gen3) link >> nda2 at nvme2 bus 0 scbus18 target 0 lun 1 >> nda2: nvme version 1.2 x4 (max x4) lanes PCIe Gen3 (max Gen3) link >> nda3 at nvme3 bus 0 scbus19 target 0 lun 1 >> nda3: nvme version 1.2 x4 (max x4) lanes PCIe Gen3 (max Gen3) link >> The disks seem to work fine, from what I can tell. >> Are the "INVALID_FIELD" messages harmless, or can they be avoided = with some tuning, or maybe with some patch? >=20 > Those messages mean that driver tried to enable certain types of = asynchronous events, but probably the hardware does not support some of = those. If you wish to experiment we could try to mask some of the bits = in nvme_ctrlr_configure_aer() function to find out which one exactly, = but for discontinued drives 4-5 years old it might not have too much = sense. It should not be critical unless you either overheat them, or = somehow else they fail and wish to report it. Thank you, Alexander. One question though: the messages report that the driver tried to set = (?) cdw10 and cdw11, but the INVALID_FIELD is about cdw0 (sorry, I have = no idea what these =E2=80=9Ccwd=E2=80=9D mean). Is that expected? = Unrelated? (The disks are Intel DC P4510, I don=E2=80=99t know how long they=E2=80=99= ve been around) Thanks, Matteo --Apple-Mail=_BE11DF7B-1C71-4899-8149-2E281E0E4131 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br = class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div = class=3D"">On May 25, 2022, at 9:58 AM, Alexander Motin <<a = href=3D"mailto:mav@FreeBSD.org" class=3D"">mav@FreeBSD.org</a>> = wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div = class=3D"">On 25.05.2022 08:25, Matteo Riondato wrote:<br = class=3D""><blockquote type=3D"cite" class=3D"">My dmesg.boot contains = the following entries containing "INVALID_FIELD" about nvme (I use = nda(4) for my nvme disks, with hw.nvme.use_nvd=3D0 in loader.conf):<br = class=3D"">trismegistus ~ % grep -e 'nvme[0-9]\?' /var/run/dmesg.boot<br = class=3D"">nvme0: <Intel DC PC4500> mem 0xb8610000-0xb8613fff irq = 40 at device 0.0 numa-domain 0 on pci7<br class=3D"">nvme1: <Intel DC = PC4500> mem 0xb8510000-0xb8513fff irq 47 at device 0.0 numa-domain 0 = on pci8<br class=3D"">nvme2: <Intel DC PC4500> mem = 0xc5e10000-0xc5e13fff irq 48 at device 0.0 numa-domain 0 on pci10<br = class=3D"">nvme3: <Intel DC PC4500> mem 0xc5d10000-0xc5d13fff irq = 55 at device 0.0 numa-domain 0 on pci11<br class=3D"">nvme0: SET = FEATURES (09) sqid:0 <a href=3D"cid:15" class=3D"">cid:15</a> nsid:0 = cdw10:0000000b cdw11:0000031f<br class=3D"">nvme0: INVALID_FIELD (00/02) = sqid:0 <a href=3D"cid:15" class=3D"">cid:15</a> cdw0:0<br = class=3D"">nvme1: SET FEATURES (09) sqid:0 <a href=3D"cid:15" = class=3D"">cid:15</a> nsid:0 cdw10:0000000b cdw11:0000031f<br = class=3D"">nvme1: INVALID_FIELD (00/02) sqid:0 <a href=3D"cid:15" = class=3D"">cid:15</a> cdw0:0<br class=3D"">nvme2: SET FEATURES (09) = sqid:0 <a href=3D"cid:15" class=3D"">cid:15</a> nsid:0 cdw10:0000000b = cdw11:0000031f<br class=3D"">nvme2: INVALID_FIELD (00/02) sqid:0 <a = href=3D"cid:15" class=3D"">cid:15</a> cdw0:0<br class=3D"">nvme3: SET = FEATURES (09) sqid:0 <a href=3D"cid:15" class=3D"">cid:15</a> nsid:0 = cdw10:0000000b cdw11:0000031f<br class=3D"">nvme3: INVALID_FIELD (00/02) = sqid:0 <a href=3D"cid:15" class=3D"">cid:15</a> cdw0:0<br class=3D"">nda0 = at nvme0 bus 0 scbus16 target 0 lun 1<br class=3D"">nda0: nvme version = 1.2 x4 (max x4) lanes PCIe Gen3 (max Gen3) link<br class=3D"">nda1 at = nvme1 bus 0 scbus17 target 0 lun 1<br class=3D"">nda1: nvme version 1.2 = x4 (max x4) lanes PCIe Gen3 (max Gen3) link<br class=3D"">nda2 at nvme2 = bus 0 scbus18 target 0 lun 1<br class=3D"">nda2: nvme version 1.2 x4 = (max x4) lanes PCIe Gen3 (max Gen3) link<br class=3D"">nda3 at nvme3 bus = 0 scbus19 target 0 lun 1<br class=3D"">nda3: nvme version 1.2 x4 (max = x4) lanes PCIe Gen3 (max Gen3) link<br class=3D"">The disks seem to work = fine, from what I can tell.<br class=3D"">Are the "INVALID_FIELD" = messages harmless, or can they be avoided with some tuning, or maybe = with some patch?<br class=3D""></blockquote><br class=3D"">Those = messages mean that driver tried to enable certain types of asynchronous = events, but probably the hardware does not support some of those. = If you wish to experiment we could try to mask some of the bits in = nvme_ctrlr_configure_aer() function to find out which one exactly, but = for discontinued drives 4-5 years old it might not have too much sense. = It should not be critical unless you either overheat them, or = somehow else they fail and wish to report it.<br = class=3D""></div></div></blockquote><br class=3D""></div><div>Thank you, = Alexander.</div><div><br class=3D""></div><div>One question though: the = messages report that the driver tried to set (?) cdw10 and cdw11, but = the INVALID_FIELD is about cdw0 (sorry, I have no idea what these = =E2=80=9Ccwd=E2=80=9D mean). Is that expected? = Unrelated?</div><div class=3D""><br class=3D""></div><div class=3D"">(The = disks are Intel DC P4510, I don=E2=80=99t know how long they=E2=80=99ve = been around)</div><div class=3D""><br class=3D""></div><div class=3D""> <div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, = 0); letter-spacing: normal; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: = break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" = class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: = break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" = class=3D""><div class=3D"">Thanks,</div><div = class=3D"">Matteo</div></div></div> </div> <br class=3D""></body></html>= --Apple-Mail=_BE11DF7B-1C71-4899-8149-2E281E0E4131--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?892F7305-97D6-4D78-B1E7-3BEC3809DD75>