x2002 Errors from Corsair P3 Plus

[pallas wept]

Hi list, 
I hope you can help.

I was quite concerned to see SMART errors from my brand new SSD this morning:

    > sudo nvme error-log /dev/nvme1
    Error Log Entries for device:nvme1 entries:16
    .................
     Entry[ 0]
    .................
    error_count     : 13
    sqid            : 0
    cmdid           : 0xa005
    status_field    : 0x2002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
    phase_tag       : 0x1
    parm_err_loc    : 0x4
    lba             : 0
    nsid            : 0x1
    vs              : 0
    trtype          : The transport type is not indicated or the error is not transport related.
    csi             : 0
    opcode          : 0
    cs              : 0
    trtype_spec_info: 0
    log_page_version: 0
    .................
     Entry[ 1]
    .................
    error_count     : 12
    sqid            : 0
    cmdid           : 0xa004
    status_field    : 0x2002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
    phase_tag       : 0x1
    parm_err_loc    : 0x4
    lba             : 0
    nsid            : 0x1
    vs              : 0
    trtype          : The transport type is not indicated or the error is not transport related.
    csi             : 0
    opcode          : 0
    cs              : 0
    trtype_spec_info: 0
    log_page_version: 0
    .................
     Entry[ 2]
    .................
    error_count     : 11
    sqid            : 0
    cmdid           : 0x18
    status_field    : 0x2002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
    phase_tag       : 0x1
    parm_err_loc    : 0x28
    lba             : 0
    nsid            : 0
    vs              : 0
    trtype          : The transport type is not indicated or the error is not transport related.
    csi             : 0
    opcode          : 0
    cs              : 0
    trtype_spec_info: 0
    log_page_version: 0
    .................
    

I've searched about this and I understand that these errors are nothing to worry about directly, but I also gather that for some devices, there was a means to avoid these errors being logged. I saw some discussion of a 'quirks' database? I'm wondering if maybe the same could be done for these devices also? They're quite popular, being Amazon's recommended NVMe drive, so maybe it's worth it.

Advice from github https://github.com/linux-nvme/nvme-cli/issues/2540#issuecomment-2430454238
suggested that I provide PCI IDs, would this help?:

08:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology P3 Plus NVMe PCIe SSD (DRAM-less) [c0a9:5421] (rev 01)


Presuming that I have correctly interpreted the issues here and nothing is really wrong, my goal here is to get a clean log when nothing is wrong, so that genuine errors would not be hidden behind the 'noise' of spurious errors.

Thanks for any advice you could offer.