x2002 Errors from Corsair P3 Plus

[Keith Busch]

On Tue, Oct 22, 2024 at 11:03:18PM +0000, pallas wept wrote:
> 
> 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.

I think you've interpreted correctly. It's most likely Identify
Controller NVM Command Set command, like everyone else. We have a flag
to make sure we don't repeatedly do it, but there's nothing that turns
it off by default. I'm pretty sure there's no way to tell if a
controller supports it or not without trying it, but since this is a
common reported problem, maybe we just quirk it off so we never try it
ever for some devices, or come up with a different criteria and
potentially skip devices that might support it.