4 ms·
Even the person submitting the report conceded that it was more to do with faulty hardware (VCC3SW malfunction) than anything wrong with memtest86. This needs t
by hd4 8y ago
Even the person submitting the report conceded that it was more to do with faulty hardware (VCC3SW malfunction) than anything wrong with memtest86. This needs to be flagged.
- TazeTSchnitzel 8y agoWhy should it be flagged? The faulty hardware is the interesting part!
- Hydraulix989 8y agolm_sensors when misused can also kill hardware by "probing" registers the wrong way when looking for sensors. https://wiki.archlinux.org/index.php/lm_sensors https://wiki.archlinux.org/index.php/lm_sensors Probing is different than testing, though, and people don't expect a general system memory testing tool to kill hardware (whereas lm_sensors has all sorts of warnings and takes the safest route possible by default). A tool that is designed to test general system RAM should not be touching memory-mapped I/O devices, and it's up to that tool to avoid them.
- deleted 8y ago[deleted]