On 7/15/20 12:11 PM, Chris Murphy wrote:
Hi,
While bad RAM is uncommon, it comes up with some regularity to cause
folks a lot of grief. I'm wondering if there's a way to make it easier
to get bad news :-\ In particular there are cases where RAM defects
just don't show up with a few hours of memtest86+, it can take days of
contiguous testing, which is so inconvenient the test itself seems
worse.
Here's what I've got so far:
1. Fedora includes /boot/memtest86+-5.01 on every installation. But
this is a legacy/BIOS program. The idea of recommending folks enable
CSM/legacy BIOS just to test their RAM is questionable because it
means disabling UEFI Secure Boot to do it. Lie in wait malware is
perhaps rare but plausible. UEFI native memtest86+ is not free so it
can't be included. I kinda wonder if including this should be
deprecated?
<Snip>
While I consider the effort to keep Memtest86+ working in Fedora pretty
heroic, and I've never had it fail to detect bad memory for me, I feel
like shipping a tool that spuriously fails on modern hardware when
attempting to detect spurious hardware failures[0][1] is more of a
negative than a positive. While it seems fixed in Rawhide, with a dead
upstream I'm sure it's just a matter of time until it happens again
(likely when the necessary GCC compat package gets dropped).
0 -
https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx/thread/6TXB3XGGHFSCYVHU54HJWMDZ2NN3UAAV/
1 - https://bugzilla.redhat.com/show_bug.cgi?id=1811353
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
