I too am seeing:
Jan 29 17:09:49 argon kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Jan 29 17:09:49 argon kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
Jan 29 17:09:49 argon kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
Jan 29 17:09:49 argon kernel: nvme0n1: I/O Cmd(0x2) @ LBA 32545872, 8 blocks, I/O Error (sct 0x3 / sc 0x71)
Jan 29 17:09:49 argon kernel: I/O error, dev nvme0n1, sector 32545872 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Jan 29 17:09:49 argon kernel: nvme 0000:01:00.0: enabling device (0000 -> 0002)
Jan 29 17:09:49 argon kernel: nvme nvme0: 4/0/0 default/read/poll queues
Jan 29 17:09:49 argon kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Pretty regularly . The system has been running for about 1 year , on&off , not 24 hours. No problem until recently. This is an Argon NEO 5 case (running bookworm) ..it's running at about 29C
Jan 29 17:09:49 argon kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Jan 29 17:09:49 argon kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
Jan 29 17:09:49 argon kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
Jan 29 17:09:49 argon kernel: nvme0n1: I/O Cmd(0x2) @ LBA 32545872, 8 blocks, I/O Error (sct 0x3 / sc 0x71)
Jan 29 17:09:49 argon kernel: I/O error, dev nvme0n1, sector 32545872 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Jan 29 17:09:49 argon kernel: nvme 0000:01:00.0: enabling device (0000 -> 0002)
Jan 29 17:09:49 argon kernel: nvme nvme0: 4/0/0 default/read/poll queues
Jan 29 17:09:49 argon kernel: nvme nvme0: Ignoring bogus Namespace Identifiers
Pretty regularly . The system has been running for about 1 year , on&off , not 24 hours. No problem until recently. This is an Argon NEO 5 case (running bookworm) ..it's running at about 29C
Statistics: Posted by graemev — Thu Jan 30, 2025 3:35 pm