#995161 linux-image-5.14.0-1-amd64: SMART error with update to 5.14 and Samsung nvme

Package:
src:linux
Source:
linux
Submitter:
Matthias Heinz
Date:
2022-05-01 11:24:03 UTC
Severity:
normal
#995161#5
Date:
2021-09-27 10:53:08 UTC
From:
To:
#995161#10
Date:
2021-09-27 11:13:37 UTC
From:
To:
Hi,

the last report was a bit short. Bugreport somehow swallowed my text.

Since I updated from 5.10 to 5.14 I'm getting a SMART error on every boot.

The nvme device is a Samsung SSD 970 EVO Plus 250GB.

The SMART error log looks like:
Error Information (NVMe Log 0x01, 16 of 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0          9     0  0x201c  0x4004      -            0     0     -

and the nvme error log says:
Error Log Entries for device:nvme0 entries:64
.................
 Entry[ 0]
.................
error_count     : 9
sqid            : 0
cmdid           : 0x201c
status_field    : 0x4004(INVALID_FIELD: A reserved coded value or an
unsupported value in a defined field)
parm_err_loc    : 0xffff
lba             : 0
nsid            : 0
vs              : 0
trtype          : The transport type is not indicated or the error is not
transport related.
cs              : 0
trtype_spec_info: 0
.................


I have verified that this error is only logged when I boot into 5.14. Booting
the older 5.10 kernel doesn't create this error (in fact the smart error log
is empty).

Best regards
Matthias
#995161#15
Date:
2021-09-28 07:53:07 UTC
From:
To:
Hi,
I have exactly the same error with Samsung 970 EVO and smart error
counter is incremented after every boot :

error_count    : 38
status_field    : 0x4004(INVALID_FIELD: A reserved coded value or an
unsupported value in a defined field)


Best regards
Edi
#995161#22
Date:
2021-11-19 09:06:19 UTC
From:
To:
Hi,
Can someone explain if this is a bug ? or maybe kernel try to talk to
nvme disk in non supported (by a disk) way ? or maybe there is a need
for some kind of exclude samsung disks from this kind of communication ?
Is anybody even working on this ?

Regards Edi
#995161#31
Date:
2022-02-06 21:40:45 UTC
From:
To:
I experienced this with 5.14 and also now in 5.15.0-0.bpo.2-amd64
#995161#36
Date:
2022-05-01 11:20:15 UTC
From:
To:
Same problem with both Samsung SSD 970 EVO Plus 250GB drives when using
5.17.0-5.1 amd64.