-
- Downloads
nvme: Add quirk for Samsung NVMe 970
It appears like the regular IRQ based suspend resume is broken for NVMe drives atleast the samsung ones causing the system not to respond after s2idle resume. Mostly it ends up timing out on the controller reset which never succeeeds. As a workaround, use a SIMPLE susped/resume pattern for the devices whose pm capabilities are broken. [ 154.173886] nvme nvme0: I/O 832 QID 1 timeout, aborting [ 154.173889] nvme nvme0: I/O 20 QID 0 timeout, reset controller [ 154.173903] nvme nvme0: I/O 833 QID 1 timeout, aborting [ 154.173909] nvme nvme0: I/O 834 QID 1 timeout, aborting [ 154.173919] nvme nvme0: I/O 835 QID 1 timeout, aborting [ 154.173924] nvme nvme0: I/O 836 QID 1 timeout, aborting [ 154.173928] nvme nvme0: I/O 837 QID 1 timeout, aborting [ 154.173933] nvme nvme0: I/O 838 QID 1 timeout, aborting [ 154.173937] nvme nvme0: I/O 839 QID 1 timeout, aborting ... [ 154.174844] nvme nvme0: Abort status: 0x371 [ 154.174878] PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -16 [ 154.175239] PM: Device 0000:03:00.0 failed to resume async: error -16 Signed-off-by:Shyam Sundar S K <Shyam-sundar.S-k@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
Loading
Please register or sign in to comment