nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed
Keith Busch
kbusch at kernel.org
Fri Dec 16 15:16:26 PST 2022
On Thu, Dec 15, 2022 at 10:38:33AM +0900, J. Hart wrote:
> 02:00.0 Non-Volatile memory controller: Kingston Technologies Device 500f
> (rev 03) (prog-if 02)
> Subsystem: Kingston Technologies Device 500f
> Flags: bus master, fast devsel, latency 0, IRQ 16
> Memory at ef9fc000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [40] Power Management version 3
> Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit+
> Capabilities: [70] Express Endpoint, MSI 00
> Capabilities: [b0] MSI-X: Enable- Count=16 Masked-
> Kernel driver in use: nvme
Seems odd that the nvme driver is in use, but MSI/MSI-x are not. We
really don't have a lot of testing with legacy IRQ.
Could you add the output from 'lspci -vvv -s 02:00.0'?
> CPU (quad core, cpu 0 shown, others the same):
>
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
> stepping : 7
That's a pretty old processor for an M.2 slotted drive. Are you using a
retimer or some type of AIC adapter card?
More information about the Linux-nvme
mailing list