Kingston KC3000 PCIe 4.0 SSD - Abort status: 0x371

[Richard Clauß]

Hello,

I opened the following issue in the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=216536

I read in another issue it is a good idea to post the issue to the 
mailing list aswell.

------------------------------------

## The following is my problem: ##

I installed a "Kingston KC3000 PCIe 4.0 SSD" of 4 Terabyte size in my 
new Ryzen 6000 Laptop "Lenovo Yoga Slim 7 Pro X".

The original SSD works fine, but the new Kingston one results in a 
delayed boot and produces errors in the kernel log. Each operation on 
the ssd is causing a delay. For example I need to wait for some time 
until "fdisk -l" responds back.

"smartctl -a" doesn't work at all:
Read NVMe Identify Controller failed: NVME_IOCTL_ADMIN_CMD: Interrupted 
system call


An excerpt of the most relevant kernel logs "dmesg | grep nvme":
[    0.815616] nvme 0000:02:00.0: platform quirk: setting simple suspend
[    0.815645] nvme nvme0: pci function 0000:02:00.0
[    1.281525] nvme nvme0: Shutdown timeout set to 10 seconds
[    1.285707] nvme nvme0: 16/0/0 default/read/poll queues
[   32.150395] nvme nvme0: invalid id 0 completed on queue 7
[   32.150404] nvme nvme0: I/O 512 (Read) QID 7 timeout, aborting
[   32.150651] nvme nvme0: Abort status: 0x0
[   62.870472] nvme nvme0: I/O 512 QID 7 timeout, reset controller
[  124.310467] nvme nvme0: invalid id 0 completed on queue 0
[  124.310490] nvme nvme0: invalid id 0 completed on queue 0
[  124.310505] nvme nvme0: invalid id 0 completed on queue 0
[  124.310520] nvme nvme0: invalid id 0 completed on queue 0
[  124.310534] nvme nvme0: invalid id 0 completed on queue 0
[  124.310548] nvme nvme0: invalid id 0 completed on queue 0
[  124.310562] nvme nvme0: invalid id 0 completed on queue 0
[  124.310576] nvme nvme0: invalid id 0 completed on queue 0
[  124.310590] nvme nvme0: invalid id 0 completed on queue 0
[  124.310605] nvme nvme0: invalid id 0 completed on queue 0
[  124.310619] nvme nvme0: invalid id 0 completed on queue 0
[  124.310634] nvme nvme0: invalid id 0 completed on queue 0
[  124.310648] nvme nvme0: invalid id 0 completed on queue 0
[  124.310662] nvme nvme0: invalid id 0 completed on queue 0
[  124.310676] nvme nvme0: invalid id 0 completed on queue 0
[  124.310690] nvme nvme0: invalid id 0 completed on queue 0
[  124.310695] nvme nvme0: I/O 8 QID 0 timeout, reset controller
[  124.327412] nvme0n1: Read(0x2) @ LBA 8001573376, 8 blocks, Host 
Aborted Command (sct 0x3 / sc 0x71)
[  124.327464] I/O error, dev nvme0n1, sector 8001573376 op 0x0:(READ) 
flags 0x80700 phys_seg 1 prio class 2
[  124.359883] nvme nvme0: Shutdown timeout set to 10 seconds
[  124.362027] nvme nvme0: 16/0/0 default/read/poll queues
[  144.913853] nvme nvme0: invalid id 0 completed on queue 2
[  155.030534] nvme nvme0: I/O 704 (Read) QID 2 timeout, aborting
[  185.750213] nvme nvme0: I/O 704 QID 2 timeout, reset controller
[  185.750274] nvme nvme0: invalid id 0 completed on queue 0
[  185.787269] nvme0n1: Read(0x2) @ LBA 8001573376, 8 blocks, Host 
Aborted Command (sct 0x3 / sc 0x71)
[  185.787363] I/O error, dev nvme0n1, sector 8001573376 op 0x0:(READ) 
flags 0x80700 phys_seg 1 prio class 2
[  185.787471] nvme nvme0: Abort status: 0x371
[  185.802599] nvme nvme0: Shutdown timeout set to 10 seconds
[  185.804537] nvme nvme0: 16/0/0 default/read/poll queues
[  267.670245] nvme nvme0: request 0x0 genctr mismatch (got 0x0 expected 
0x1)
[  267.670332] nvme nvme0: invalid id 0 completed on queue 0
[  267.670343] nvme nvme0: I/O 24 QID 0 timeout, reset controller
[  267.710387] nvme0: Identify(0x6), Host Aborted Command (sct 0x3 / sc 
0x71)
[  267.726065] nvme nvme0: Shutdown timeout set to 10 seconds
[  267.729259] nvme nvme0: 16/0/0 default/read/poll queues
[  806.976986] nvme nvme0: invalid id 0 completed on queue 7
[  806.977004] nvme nvme0: I/O 513 (Read) QID 7 timeout, aborting
[  806.977236] nvme nvme0: Abort status: 0x0

The attachment is a .tar.xz containing command outputs of:
"smartctl -a ", "fdisk -l", "dmesg | grep nvme", "lspci -vv", "dmesg", 
"journalctl -b"

My main question:
Is it possible to determine if this is a kernel issue or is it a 
hardware issue and can it be solved?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: command_outputs.tar.xz
Type: application/x-xz
Size: 35928 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20220928/71d52e7e/attachment-0001.xz>