From nobody Wed May 25 13:58:54 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 62E331B49AE1 for ; Wed, 25 May 2022 13:59:04 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 4L7Xjg3KCQz3jV4; Wed, 25 May 2022 13:59:03 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: by mail-qk1-x72d.google.com with SMTP id j6so17343605qkp.9; Wed, 25 May 2022 06:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=YF+kB1Iy8IY0vfXlBSXrzmjMclm0F4wpn86oIuNL+/0=; b=aQLWdgs8YZRbsMFaFB33t0SYFqejpewkJYoCVM/BaoPL6LfaHX/mEhNuASIUlQHfNa OMYN8RaNauFsVlNH5O6+R/E2bi09XLpTr6ziiILGcaBh9PoTp2NmQOLPY1axrXMk2jaY 6tELKZpqD7U1SWAacaZ1ueGeCeJOjQTb69gMEMmvptnr603qmAFOliZ78Yn3rALl4baI uk55/yXeaDHLnetWdSJy03ur6LRC0X4Ux6y/Q33VmlhW6cMiXWtHhKJo9UZbtYwb2xQa lUyEchHKKALkHA/5k8jFQ6k+HjhDfqly7MCRUamhNV+mnN2Fs0jrMvYsbEt+3M/A319X cQPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:message-id:date:mime-version:user-agent :subject:content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=YF+kB1Iy8IY0vfXlBSXrzmjMclm0F4wpn86oIuNL+/0=; b=7joitKthWGd7lzNLOY1VOAI+jAI1MlR8dyNcnyD0S99bzCf0lLTKURYkc6e1xKnyMa PPtZ9iBWkPinEPr2VzDaqMkjH4fK6KsgqnXfSc8bfOWyNrzijcb6oAI9SLCyyFKiMbK9 U0QstSlW64lajTYKoaL7t4xAm2VUdSz6RAbLz/0caLP0WqhldIOqlsa7XVoESIdvDkAC cAAxtdilIrrJ8b9GbUZ98vcwQ57irPrNbRQHHVhlSPhtJgTG+Wd2a2m+gyJNxQA7KGpy BFoHvMCWtJX0dsapa3UTrKsxvft1lhZPKXEP9twGncpbSrgdIlYFYy9mA7F3yXsfnHX1 uYcA== X-Gm-Message-State: AOAM530F8FIQh5PYvJfC0Kfn6ltojLoGPzGP2+hfSNmr2P2u7MUsTJME 9pz3lys9rRJtZ3UVrztYGX+pQBj1o4E= X-Google-Smtp-Source: ABdhPJxKvyReL915WyxHvwUJHevxLJrT7ItziJx1+LVqYclsIg3iqYsSwjrF0Nhvn/Al0lzJUPW0Kg== X-Received: by 2002:a37:b42:0:b0:6a3:6133:674c with SMTP id 63-20020a370b42000000b006a36133674cmr14401690qkl.325.1653487136607; Wed, 25 May 2022 06:58:56 -0700 (PDT) Received: from ?IPV6:2603:3011:17c0:0:228:f8ff:fe04:d12? ([2603:3011:17c0:0:228:f8ff:fe04:d12]) by smtp.gmail.com with ESMTPSA id i75-20020a379f4e000000b006a38debe62csm1324418qke.89.2022.05.25.06.58.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 25 May 2022 06:58:55 -0700 (PDT) Message-ID: Date: Wed, 25 May 2022 09:58:54 -0400 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: nvme INVALID_FIELD in dmesg.boot Content-Language: en-US To: Matteo Riondato , freebsd-current@freebsd.org Cc: Jim Harris References: <20220525122529.t2kwfg2q65dfiyyt@host-ubertino-mac-88e9fe7361f5.eduroam.ssid.10net.amherst.edu> From: Alexander Motin In-Reply-To: <20220525122529.t2kwfg2q65dfiyyt@host-ubertino-mac-88e9fe7361f5.eduroam.ssid.10net.amherst.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4L7Xjg3KCQz3jV4 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=aQLWdgs8; dmarc=none; spf=pass (mx1.freebsd.org: domain of mavbsd@gmail.com designates 2607:f8b0:4864:20::72d as permitted sender) smtp.mailfrom=mavbsd@gmail.com X-Spamd-Result: default: False [-2.87 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[FreeBSD.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[gmail.com:+]; NEURAL_HAM_SHORT(-0.67)[-0.671]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72d:from]; MLMMJ_DEST(0.00)[freebsd-current]; FORGED_SENDER(0.30)[mav@FreeBSD.org,mavbsd@gmail.com]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[mav@FreeBSD.org,mavbsd@gmail.com]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N 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=0 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? 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. -- Alexander Motin