similar to: x86_64 EDAC throwing error

What does the following EDAC problem means? The machine is a AMD 64bit box running Centos 5. It looks like some problems aroung AMD DRAM Memory controller. But what does it really mean b/c most of my AMD boxes has these messages in /var/log/messages. Please help. ... Aug 1 23:29:40 ccn128 kernel: EDAC MC: Ver: 2.0.1 Jun 12 2007 Aug 1 23:29:40 ccn128 kernel: EDAC MC0: Giving out device to

Dear CentOS community, Can someone give me clues as to whether my memory is going bad or I am having problem with the actual board. Thank you in advace. I am getting the following error via stdout and also in /var/log/messages Aug 15 20:37:10 saturn kernel: Northbridge Error, node 0 Aug 15 20:37:10 saturn kernel: ECC/ChipKill ECC error. Aug 15 20:37:10 saturn kernel: EDAC amd64 MC0: CE

After update from centos 6.6 to centos 6.7 and reboot it, I have get a lot of this error into /var/log/messages: > May??3 11:27:20 s-virt kernel: EDAC MC0: CE row 2, channel 1, label > "": (Branch=0 DRAM-Bank=2 RDWR=Read RAS=6093 CAS=896, CE Err=0x10000 > (Correctable Patrol Data ECC)) > May??3 11:27:21 s-virt kernel: EDAC MC0: CE row 2, channel 1, label > "":

Hi List, We had the following error thrown on console on a PowerEdge server running CentOS 5 (64 bit). Googling around didn't yield any particular insights. The server crashed a few minutes after this message. Running memtester, just to check, didn't find anything; and the box has been running for months before this without issue. I'm wondering if anyone has run across this

I've got a production system running CentOS 4 that was rock solid until I upgraded from 2.6.9-55 to 2.6.9-78.0.13 (now running 2.6.9-89.0.11). The system now crashes intermittently after a few weeks. I finally caught the panic message : EDAC MC0: INTERNAL ERROR: channel-b out of range (4 >= 4) Kernel panic - not syncing: MC0: Uncorrected Error Looking at the kernel changelog, I see that

Am 21.01.16 um 17:41 schrieb Jan Beulich: >>>> On 20.01.16 at 16:01, <andreas.pflug at web.de> wrote: >> Initially reported to debian >> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810964), redirected here: >> >> With AMD Opteron 6xxx processors, half of the memory controllers are >> missing from /sys/devices/system/edac/mc >> Checked

Dear All, I have problem with CentOS 6 64bit, this screen monitor view below EDAC MC0 : UE row 0, channel-a= 0 channel-b= 1 labels "-" (Branch= 0 DRAM RAM Bank= 2 RDWR=Write RAS=14316 CAS=0 FATAL Err=0x4 (> Tmid Thermal event with intelligent throttling disabled )) but, now this server running very well. Maybe know the couse of error. Thank you very much before. --

I haven't yet done as much experimentation as Andreas Pflug has, but I can confirm I'm also running into this bug with Xen 4.4.1. I've only tried Linux kernel 3.16.43, but as Dom0: EDAC MC: Ver: 3.0.0 AMD64 EDAC driver v3.4.0 EDAC amd64: DRAM ECC enabled. EDAC amd64: NB MCE bank disabled, set MSR 0x0000017b[4] on node 0 to enable. EDAC amd64: ECC disabled in the BIOS or no ECC

Hi List, I've been getting the following EDAC memory errors EDAC MC0: CE page 0xeb0dd, offset 0x0, grain 4096, syndrome 0x45, row 3, channel 0, label "": i82875p CE and from this seeing that these errors have been corrected. Checking cat /sys/devices/system/edac/mc/mc0/csrow3/ch0_ce_count gives me a count of 4 thus I now know that csrow3 - ch0 is the problem My question is, how

Hello, We have recently purchased two Supermicro servers, AS-1021M-T2RB (http://www.supermicro.com/Aplus/system/1U/1021/AS-1021M-T2RV.cfm), and have built them both with CentOS 5 operating system. They are identical, apart from the manufacturer of the disk drives. Kernel is: Linux version 2.6.18-8.1.6.el5 (mockbuild at builder6.centos.org) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u3 Debian 8.2 installed on a supermicro H8SGL Board, AMD 6128 with 4x4GB ECC RAM. When booting the plain kernel (stock Jessie 3.16 or backport 4.1 or 4.3), both memory controllers (mc0 and mc1) appear under /sys/devices/system/edac/mc with two csrow* each as expected. Same happens, when booted with Xen 4.1.4-3+deb7u1. When booted with Xen

Initially reported to debian (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810964), redirected here: With AMD Opteron 6xxx processors, half of the memory controllers are missing from /sys/devices/system/edac/mc Checked with single 6120 (dual memory controller) and twin 6344 (2x dual MC), other dual-module CPUs might be affected too. Booting plain Linux (3.2, 3.16, 4.1, 4.3), all memory

Hey, folks, I've got an HP Proliant DL580 G5 throwing ECC errors. This is annoying, since a) it's all new as of a few months ago, and b) it's *fully* populated. The two things I need to figure out are a) *which* DIMM it is, and b) is it mirrored; if so, which *other* DIMM needs to come out until we get replacements from the OEM. Here's one of many, all identical, from dmesg:

Hi, I updated a server yesterday from "kernel 2.6.18-128.7.1.el5xen" to "kernel 2.6.18-164.el5xen" After rebooting, my message log is flooded every second or so with this error messages: Oct 6 14:52:20 xenserver1 kernel: EDAC MC0: UE row 0, channel-a= 0 channel-b= 1 labels "-": NON-FATAL recoverable (Branch=0 DRAM-Bank=0 Buffer ID = 0 RDWR=Read RAS=0 CAS=0

Hi All, I am having issue when trying to build a custom kernel in CentOS 4.4. Current Kernel Version is 2.6.9-42.ELsmp and the server is HP Proliant DL380 G3. I downloaded the source rpm and then installed it. Gave the command, rpmbuild -bp --target=i686 /usr/src/redhat/SPECS/kernel-2.6.spec. But it throws me an error after patch operations. The following is the error.

Hi all, I ve setup a queue with 2+ agents for managing our inbound calls from customer. Using Asterisk 1.2.18 in a CentOS box. Agents login using AgentCallbackLogin application and I use a BASH AGI to accomplish this as there are some validations done with MySQL DB. Im aware that transfer could be done with option 't' in the queue() application and I was able to successfully transfer

In order to support ZFS, we upgraded a backups server with a new, ECC motherboard. We're running CentOS 6 with ZFS on Linux, recently patched. Now, I want to enable EDAC so we can check for memory errors (and maybe PCI errors as well) but so far, repeatedly pounding on the Google hasn't yielded exactly what I need to do to enable EDAC. One howto was covering PCI and edac, but

Hi, Which is the recommended filesystem to be used for the bricks in glusterFS. ?? XFS/EXT3/EXT4 etc .???? Thanks & Regards, Bobby Jacob Senior Technical Systems Engineer | eGroup P SAVE TREES. Please don't print this e-mail unless you really need to. -------------- next part -------------- An HTML attachment was scrubbed... URL:

CentOS Errata and Bugfix Advisory 2014:0768 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0768.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f9238919a8e55753462b1690cc36a16b0a0c29260663dd5fe3e9ee0ae7a187c9 edac-utils-0.9-15.el6.i686.rpm

Hi All, Is there a way that I can include call dialing functionality in a webinterface. I have EyeBeam configured with a SIP user say 8440. Will I be able to design an inteface which agent can choose a number and the Dial without punching in the number in Eyebeam. I tried using the .call file. ie The agent can choose which number to dial from a web interface. Then, a .call file is created with