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 th
That works perfectly well until the next reboot. I just tried it, and it
certainly stops the error messages being added to the log, with no other
observable effect. It does leave the edac_core module still loaded, so
to get the same effect as a blacklist/reboot you would also need to do
"rmmod edac
Oops, sorry, I was confusing you with Marty Lucich who mentioned
i82975x! And I am obviously out of date with my module management.
OK, I created myself a file named /etc/modprobe.d/edac.conf that contains one
line:
blacklist x38_edac
and after reboot I no longer see any EDAC messages on my
I see the fix 100% of the time (in fact I do it about once a day, every
time I turn on my PC), so it would seem we have different problems.
Can you turn off EDAC reporting by creating a file named /etc/modprobe.d/edac
that reads:
alias i82975x_edac off
and then rebooting?
--
EDAC spam in dm
Does running memtest86+ fix things until the next cold boot?
--
EDAC spam in dmesg, edac-utils shows no erros
https://bugs.launchpad.net/bugs/367774
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Just for the record, I too am seeing this behavior (Gigabyte GA-X48-DS4
motherboard). However, I don't see it with an ASUS P5E motherboard (all
the other components being the same, swapped to test the different
motherboard).
Also, if I run memtest86+ for a few seconds (just long enough to make a
c
