Re: nvme INVALID_FIELD in dmesg.boot

On Wed, May 25, 2022 at 6:59 AM Alexander Motin wrote: ... > > nvme0: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:000b cdw11:031f > > 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 probabl

Re: nvme INVALID_FIELD in dmesg.boot

On Wed, May 25, 2022 at 9:39 AM Matteo Riondato wrote: > On 2022-05-25 at 11:29 EDT, Warner Losh wrote: > > > >SET FEATURES (opcode 9) feature 0xb is indeed async event > >configuration. > >0x31f is: > >SMART WARNING for available spares (0x1) > >SMART warning for temperature (0x2) > >SMART WARN

Re: nvme INVALID_FIELD in dmesg.boot

Here's a patch that might fix it diff --git a/sys/dev/nvme/nvme_ctrlr.c b/sys/dev/nvme/nvme_ctrlr.c index 2c5d521ecaa1..72c511de3be8 100644 --- a/sys/dev/nvme/nvme_ctrlr.c +++ b/sys/dev/nvme/nvme_ctrlr.c @@ -854,8 +854,9 @@ nvme_ctrlr_configure_aer(struct nvme_controller *ctrlr) NVME_C

Re: nvme INVALID_FIELD in dmesg.boot

On 2022-05-25 at 11:29 EDT, Warner Losh wrote: SET FEATURES (opcode 9) feature 0xb is indeed async event configuration. 0x31f is: SMART WARNING for available spares (0x1) SMART warning for temperature (0x2) SMART WARNING for device reliability (0x4) SMART WARNING for being read only (0x8) SMA

Re: nvme INVALID_FIELD in dmesg.boot

On Wed, May 25, 2022 at 8:18 AM matti k wrote: > On Wed, 25 May 2022 09:58:54 -0400 > Alexander Motin 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 > >

Re: nvme INVALID_FIELD in dmesg.boot

> On May 25, 2022, at 9:58 AM, Alexander Motin 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=0 in >> loader.conf): >> trismegistus ~ % grep -

Re: nvme INVALID_FIELD in dmesg.boot

On Wed, 25 May 2022 09:58:54 -0400 Alexander Motin 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=0 in loader.conf): > > > > trismegistus ~ %

Re: nvme INVALID_FIELD in dmesg.boot

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 0xb861-0xb8613fff i

Re: nvme INVALID_FIELD in dmesg.boot

On Wed, May 25, 2022 at 5:26 AM Matteo Riondato wrote: ... > nvme0: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:000b > cdw11:031f > nvme0: 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

Re: (263489) (D35109) freebsd-update: restart sshd after upgrade

On Mon, 2 May 2022 at 20:17, Graham Perrin wrote: > > > (line 3028) > > How will freebsd-update behave in this case? > > > Cannot 'sta

nvme INVALID_FIELD in dmesg.boot

Dear list, 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 0xb861-0xb8613fff irq 40 at device 0.0 numa-domain