This doug thompson, maintainer of EDAC Output such as:
[252875.478201] EDAC MC0: UE page 0x1f8ba, offset 0x0, grain 4096, row 0, labels ":": i82875p UE [252876.477136] EDAC MC0: UE page 0x1f8ba, offset 0x0, grain 4096, row 0, labels ":": i82875p UE [252877.476067] EDAC MC0: UE page 0x1f8ba, offset 0x0, grain 4096, row 0, labels ":": i82875p UE [252878.475003] EDAC MC0: UE page 0x1f8ba, offset 0x0, grain 4096, row 0, labels ":": i82875p UE [252879.473936] EDAC MC0: UE page 0x201b, offset 0x0, grain 4096, row 0, labels ":": i82875p UE [252880.472871] EDAC MC0: UE page 0x1f8ba, offset 0x0, grain 4096, row 0, labels ":": i82875p UE [252881.471816] EDAC MC0: UE page 0x201b, offset 0x0, grain 4096, row 0, labels ":": i82875p UE [252882.470740] EDAC MC0: UE page 0x1f8ba, offset 0x0, grain 4096, row 0, labels ":": i82875p UE [252883.469673] EDAC MC0: UE page 0x2000, offset 0x0, grain 4096, row 0, labels ":": i82875p UE [252884.468608] EDAC MC0: UE page 0x201b, offset 0x0, grain 4096, row 0, labels ":": i82875p UE IS the EDAC chipset driver issuing error messages. But EDAC does NOT issue BEEPs as a warning. Rather just output to /var/log/messages and info in sysfs /sys/devices/system/edac/..... The UE above stands for UN-CORRECTED ERROR The chipset is detecting an UE event and EDAC is simply logging the error event. I suspect the BEEPING is occurring from the BIOS code. Some Intel mobos have hidden event handling code within the BIOS, even under Linux. The UE handler in the BIOS then could be issuing the BEEPS As to why the machine has not failed or crashed, I don't know. ECC errors are a funny bunch events I assert that you have a bad memory DIMM. If the LABELS were set on this mobo, then one could gather which DIMM it is. Labels are set in the sysfs directory for the CSROWS of the DIMM EDAC is simply the kernel's harvester of hardware detections for ECC events. These events (EDAC warnings and BIOS BEEPS) are simply hairy BIG RED FLASHING lights indicating there is a fire and one should do something about it. This assumes that the low level driver is functioning, true. First step is to get another DIMM and try each of the DIMMS you have with a new one, or remove all memory but one DIMM and reboot Try all your DIMMs one at a time to check for the warning by reboot on each one. If just one DIMM has the warning, that is your bad guy. If you have lifetime warranty DIMMs, then RMA it. Always nice to have a spare If two have warnings and others don't then those two are bad If every DIMM has a warning THEN there might be a problem with the driver that needs testing, but I no longer have such a mobo. I inherited that driver when I took up the project. Please response here and/or to [EMAIL PROTECTED] thanks doug t -- error in terminal after upgrading to Feisty https://bugs.launchpad.net/bugs/113793 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
