Latest.
Add nvme_core.default_ps_max_latency_us=2500
to /boot/firmware/cmdline.txt
dmesg | grep nvme
I see same messages as I previously posted. In addition, the following messages are new.
nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
nvme nvme0: Does your device has a faulty power saving mode enabled?
nvme nvme0: Try "nvme_core.deflault_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
Modify cmdline.txt as suggested nvme_core.deflault_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off
reboot
Now, using lsblk and the nvme doesn't show up.
Do a shutdown.
Same results. lsblk and the nvme doesn't show up.
Remove the modifications to cmdline.txt. Reboot
Same results. lsblk and the nvme doesn't show up.
dmesg | grep nvme doesn't return anything.
Add nvme_core.default_ps_max_latency_us=2500
to /boot/firmware/cmdline.txt
dmesg | grep nvme
I see same messages as I previously posted. In addition, the following messages are new.
nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
nvme nvme0: Does your device has a faulty power saving mode enabled?
nvme nvme0: Try "nvme_core.deflault_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
Modify cmdline.txt as suggested nvme_core.deflault_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off
reboot
Now, using lsblk and the nvme doesn't show up.
Do a shutdown.
Same results. lsblk and the nvme doesn't show up.
Remove the modifications to cmdline.txt. Reboot
Same results. lsblk and the nvme doesn't show up.
dmesg | grep nvme doesn't return anything.
Statistics: Posted by ipmaercyrrebpsar — Thu Jan 16, 2025 12:23 am