Comment 4 for bug 2039601

Failure manually transcribed:

kernel: nvme nvme0: controller is down; will reset: CSTS:0xffffffff, PCI_STATUS=0xffff
kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
kernel: nvme nvme0: try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
kernel: nvme 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible
kernel: nvme nvme0: Disabling device after reset failure: -19
mount[353]: mount /sysroot: can't read suprtblock on /dev/nvme0n1p5.
mount[353]: dmesg(1) may have more information after failed moutn system call.
kernel: nvme0m1: detected capacity change from 2000409264 to 0
kernel: EXT4-fs (nvme0n1p5): unable to read superblock
systemd([1]: sysroot.mount: Mount process exited, code=exited, status=32/n/a
...

All kernels are upstream, untainted and compiled on Arch linux using:

 gcc version 13.2.1

Kernels Tested:
 - 6.4.10 - works fine
 - 6.5-rc6 - fails
 - 6.4.11 with 1 revert also fails

    Revert "nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G and 512G"

    This reverts commit 061fbf64825fb47367bbb6e0a528611f08119473.

Hardware:
  model name : Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  stepping : 9
  microcode : 0xf4

nvme:
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963

All tests on dell laptop running Arch. All