M.2 NVME controller is down

Hi NV Support Team
Do you have any patch to fix the below issue?

[ 18.393981] EXT4-fs (nvme0n1): mounted filesystem with ordered data mode. Opts: (null)
[ 2694.644744] nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x2010
[ 2694.762092] nvme nvme0: Shutdown timeout set to 10 seconds
[ 2694.768435] nvme nvme0: 12/0/0 default/read/poll queues
[ 2725.368250] nvme nvme0: I/O 320 QID 9 timeout, disable controller
[ 2725.439493] blk_update_request: I/O error, dev nvme0n1, sector 526270464 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
[ 2725.451059] EXT4-fs warning (device nvme0n1): ext4_end_bio:345: I/O error 10 writing to inode 7602820 starting block 65785856)
[ 2725.462791] blk_update_request: I/O error, dev nvme0n1, sector 526225408 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
[ 2725.462834] Buffer I/O error on device nvme0n1, logical block 65783808
[ 2725.474350] blk_update_request: I/O error, dev nvme0n1, sector 526224384 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0

Thanks
Yutai

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

Are you using custom carrier board or devkit?
Which JetPack SW?
How this issue was reproduced?

Thanks

1 Like