My experience (yours may be different) is that running a NVMe board with the PICE at Gen 3 results in a significant number of warning messages in the journal...The most I've seen is 22,000 of these messages in a day. So far they are all "Corrected error", but on my primary storage device I would be happier to see zero errors (even corrected ones). So far I've not seen any "Uncorrected error" messages. That's why I've dropped mine to Gen2 speed which gives a zero error rate. And it's still "WOW!" fast ![:-)]( "Smile")
Of course a different NVMe board with a different SSD may give different results, but don't forget there must be a reason that RPL don't claim Gen 3 compliance. A friend with access to the appropriate professional level test equipment says the level of "clock jitter" is "close to the edge" and that may be the reason for non-compliance at Gen 3. The thing about it being "jitter" means that it is going to be ok some (*) of the time.
PeterO
(*) for some value of "some" between 0% and 100%![:-)]( "Smile")
PS:
I dropped it to Gen 2 early on Dec 27th when I first noticed the messages in the journal.
PeterO
Code:
Dec 23 18:45:02 pi-nvme kernel: pcieport 0000:00:00.0: AER: Corrected error received: 0000:00:00.0Dec 23 18:45:02 pi-nvme kernel: pcieport 0000:00:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)Dec 23 18:45:02 pi-nvme kernel: pcieport 0000:00:00.0: device [14e4:2712] error status/mask=00000040/00002000Dec 23 18:45:02 pi-nvme kernel: pcieport 0000:00:00.0: [ 6] BadTLP 
Of course a different NVMe board with a different SSD may give different results, but don't forget there must be a reason that RPL don't claim Gen 3 compliance. A friend with access to the appropriate professional level test equipment says the level of "clock jitter" is "close to the edge" and that may be the reason for non-compliance at Gen 3. The thing about it being "jitter" means that it is going to be ok some (*) of the time.
PeterO
(*) for some value of "some" between 0% and 100%
PS:
Code:
for a in 22 23 24 25 26 27 28 29 30 31 ; do echo -n "Dec $a " ; journalctl | grep "Corrected error" | grep "Dec $a" | wc -l ; doneDec 22 0Dec 23 213Dec 24 66Dec 25 14Dec 26 22111Dec 27 7Dec 28 0Dec 29 0Dec 30 0Dec 31 0PeterO
Statistics: Posted by PeterO — Tue Jan 02, 2024 9:30 am