Comment 14 for bug 367774

What is not working is really your BIOS; the GIGABYTE engineers have been aware of the problem with their BIOSes since it was reported to them back in April, but to date they have been unable to correct the problem. I have no idea if they are still trying, or if they have decided it is not worth the effort. On the other hand, the ASUS motherboards using the same chipset don't suffer from this problem. Not sure about any other brands?

It would be possible for the EDAC module to work around the BIOS bug by initializing all memory at startup, or at least to avoid infinitely repeated errors by scrubbing (either scrubbing all memory in the background, or at least scrubbing each address that reported an error).

However, I would not like to see the default changed to not reporting the errors - not unless the problem motherboards could be identified, and the default changed only for the motherboards with the bad BIOSes...