From nobody Wed May 25 14:32:05 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id F29CA1B5439C for ; Wed, 25 May 2022 14:32:08 +0000 (UTC) (envelope-from rionda@gmail.com) Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4L7YRr0n6dz3stt; Wed, 25 May 2022 14:32:08 +0000 (UTC) (envelope-from rionda@gmail.com) Received: by mail-qk1-x72c.google.com with SMTP id t2so13315118qkb.12; Wed, 25 May 2022 07:32:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=SsSEfG+VMHHWJTzshKUU1M/o+4a+LOdM3TFVPwa7+Hc=; b=kvRb0UZC2+hygLJXWtsG80PO2m4rSxZ2exIfEyypqqNHTRVIXvKCiobhyzxPxMeXbg 1+0zMvHcuQV9JHI+Y3NEvxLyKnYP+ee2V+hg5+YOxlKwIk6lMFtVCDiHviswrnmG742O IMlaGoYWBom0Vu4YtafkS4kwNMuHBLuLeovOq7UHyBY5r8WoD4c5mKzrB2uVlo8c8WCH l1TJoByEUp1rZazfHnLuDLTuqwsG81Jjp4jJD1wMjh6DrwW8kuzev4KxysToFz+2lKo8 GEq20iKfQ9fKAC5pbm3psZJEDv9eyfNvYdp7t5NSutBgqaMqSiXOqdg1rTObmkizqBoZ KjRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=SsSEfG+VMHHWJTzshKUU1M/o+4a+LOdM3TFVPwa7+Hc=; b=5fQEXzdhWeULhuyMTP3YOAI+QNMLEFqOLh/usnJmyjqtQ5YbV2lDd0An5feqGyyE0a eXxiBqIWxFk7duEeA3YSN8ekQMmeIkQ3nBYg3PFQoXauxeB6+JJdXR3sECoyNmYhONMm m66OfncHgGSobcozJnuAht00nrI9TbpA10S3DMz8OVponUAXX1+6BJ2Tbf7ikdoSLa0K qo3MxzLDgXmlG5QCZuvpJihKBi7yqCxHHl2N81bIjirVg6qBXFndqHkoNlFhfkcGIHMO 5Uk2Sn3IjkxZprVisF6RVseVO+X3j9YVi7irdENnfASHwZjLEuV0SNJmlnPaIU2rBJiJ WMPQ== X-Gm-Message-State: AOAM532TKAWUJbF4l352zGqJIKXGGMKIHApNt55wnbWM8u0Q5i8eC5Pf qBP/F/X4k0FxFWLZGbBxw2UXLds0BkU= X-Google-Smtp-Source: ABdhPJyYtQ09avrRdDWh5fbNZiEkac5oqNIbFfiVHh2vCQ+Qm4WpJGFjCaBNqibHbrvX9F0janLyKw== X-Received: by 2002:a37:bf06:0:b0:6a3:4100:8456 with SMTP id p6-20020a37bf06000000b006a341008456mr18718991qkf.423.1653489127137; Wed, 25 May 2022 07:32:07 -0700 (PDT) Received: from smtpclient.apple ([2601:19b:4400:1779::107b]) by smtp.gmail.com with ESMTPSA id v4-20020ac873c4000000b002f906fc8530sm1362191qtp.46.2022.05.25.07.32.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 May 2022 07:32:06 -0700 (PDT) From: Matteo Riondato Message-Id: <892F7305-97D6-4D78-B1E7-3BEC3809DD75@FreeBSD.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_BE11DF7B-1C71-4899-8149-2E281E0E4131" List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) Subject: Re: nvme INVALID_FIELD in dmesg.boot Date: Wed, 25 May 2022 10:32:05 -0400 In-Reply-To: Cc: freebsd-current@freebsd.org, Jim Harris To: Alexander Motin References: <20220525122529.t2kwfg2q65dfiyyt@host-ubertino-mac-88e9fe7361f5.eduroam.ssid.10net.amherst.edu> X-Mailer: Apple Mail (2.3696.100.31) X-Rspamd-Queue-Id: 4L7YRr0n6dz3stt X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=kvRb0UZC; dmarc=none; spf=pass (mx1.freebsd.org: domain of rionda@gmail.com designates 2607:f8b0:4864:20::72c as permitted sender) smtp.mailfrom=rionda@gmail.com X-Spamd-Result: default: False [-0.90 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; FORGED_SENDER(0.30)[matteo@FreeBSD.org,rionda@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[matteo@FreeBSD.org,rionda@gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[FreeBSD.org]; NEURAL_SPAM_SHORT(0.80)[0.797]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72c:from]; MLMMJ_DEST(0.00)[freebsd-current]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --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 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: mem 0xb8610000-0xb8613fff irq 40 at device = 0.0 numa-domain 0 on pci7 >> nvme1: mem 0xb8510000-0xb8513fff irq 47 at device = 0.0 numa-domain 0 on pci8 >> nvme2: mem 0xc5e10000-0xc5e13fff irq 48 at device = 0.0 numa-domain 0 on pci10 >> nvme3: 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

On May 25, 2022, at 9:58 AM, Alexander Motin <mav@FreeBSD.org> = wrote:

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?

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=99ve = been around)

Thanks,
Matteo

= --Apple-Mail=_BE11DF7B-1C71-4899-8149-2E281E0E4131--