3 ms·
On my current desktop machine (32GB ECC DRAM) I see a single bit error (corrected) probably every 18 to 20 days. There isn't an easy way to tell where that erro
by ChuckMcM 10y ago
On my current desktop machine (32GB ECC DRAM) I see a single bit error (corrected) probably every 18 to 20 days. There isn't an easy way to tell where that error hit in memory (you could presumably walk it back from the physical chip to the physical address space to the current page table and then back into virtual space and a process but that is waaaaaaaay too much work :-) Without ECC those errors would happen and I'd keep working and they may or not cause a visible symptom. A schematic data base slightly corrupted when it was saved to disk, a Flash image that isn't quite right, a system daemon that crashes and restarts unexpectedly, etc. Not really something I want to take my chances on.
Of course if you don't have ECC memory you don't know that your memory is being silently corrupted. For some people they don't care, for me, I do.
- effie 10y agoHow are you able to "see" the single bit errors? I had an ECC machine but I couldn't find any indication that ECC was working or that any bit errors happened. Reading this I thought the best I could do is to believe that workstation with ECC modules and Xeon will have functioning ECC: "Unfortunately, we have found that there is no consistent, conclusive way to determine if ECC RAM is working properly. ...We've actually asked Intel, Kingston and Asus over the years for their recommendations for methods to confirm that ECC is working, but we haven't gotten much more back than a blank stare." https://www.pugetsystems.com/labs/articles/How-to-Check-ECC-RAM-Functionality-462/#Conclusion https://www.pugetsystems.com/labs/articles/How-to-Check-ECC-...
- ChuckMcM 10y agoThe BIOS has to correct them, you get what is essentially a machine check, the BIOS fixes the error, does the writeback, and in my case logs the fix on the system management (SMB) bus and that shows up in the IPMI system event log[1]. Not sure who the BIOS would tell if there wasn't some sort of BMC chip to hear about it, it might keep an internal log. I'm surprised the board/bios manufacturer couldn't answer the question, it's a pretty straight forward system. [1] They show up as 'SBE' events (single bit error). An 'MBE' event (detectable but not correctable) would presumably result in an unhandled machine check and cause the kernel to reboot.
- effie 10y agoThat's interesting. Is it possible to use IPMI and log BMC events on a regular workstation from Dell or Lenovo, perhaps via some expansion card? Or is this only a server-grade feature?
- fulafel 10y agoThey're also logged by some portable mechanism on normal x86 boards, viewable at least using the "mcelog" tool under Linux, and probably logged by the kernel in the normal kernel event log. I think the mce log is supposed to persist over reboots so you could see the multibit error afterwards if you got a machine check induced reboot.
- deleted 10y ago[deleted]
- wmf 10y agoLinux has drivers that receive ECC notifications from the hardware and the edac-util command should display them. You can cause bit errors with a hair dryer and see if Linux recognizes them: http://bluesmoke.sourceforge.net/heat_gun.html http://bluesmoke.sourceforge.net/heat_gun.html
- unwind 10y agoIf you think that link is about hairdryers, I really suggest you do some shopping. You'll find less smoldering, better smell, and less pain if you use an actual hair dryer to dry your hair (rather than a heat gun, which the page is about).
- effie 10y agoThanks a lot! I'll probably try both after I get my machine working again.