similar to: DIMM problem

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

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 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 started to receive this kind of messages a few days ago on one of my servers: Message from syslogd@ at Mon Apr 29 08:02:55 2013 ... server1 kernel: EDAC MC0: UE row 0, channel-a= 0 channel-b= 1 labels "-": (Branch=0 DRAM-Bank=0 RDWR=Read RAS=0 CAS=0, UE Err=0x2 (Aliased Uncorrectable Non-Mirrored Demand Data ECC)) I've never had ECC memory to fail on me before, so now I am

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 > "":

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

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

Hi All, We have installed CentOS 5.3 x86_64 in an HP DL585 server with AMD Opteron 64 bit processor and 16 GB RAM. The kernel version is 2.6.18-128.el5 . Now this has thrown an error message in /var/log/message, Jul 3 21:41:11 db1 kernel: EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem

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

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

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

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

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

Hi, Thanks for your mail, and time It is not working for some arguments, when mean value is like >6. case mc0 <- c(0.08844446,0.1744455,0.1379778,0.1209769,0.1573065,0. 1134463,0.2074027) rv <-UnivarMixingDistribution(Norm(486.4255, 53.24133), Norm(664.0713, 3.674773), Norm(669.0484, 4.101381),

Hi, I've found out that NVDIMM size and label size matter for regular (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the guest OS will not accept the hot plugged memory and will complain with messages such as Block size [0x8000000] unaligned hotplug range: start 0x225000000, size 0x10000000 The start address above is also reported within <memory> element of the hot

Dear list, Given a linear mixed model (from lme4) I want to 1) first change the input dataset and then 2) change the model formula. I want this to happen in a function call; Please see below. Options 1) and 2) below work whereas 3) fails with the message > foo() Error in is.data.frame(data) : object 'beets2' not found Question: What is it one must to in case 3) to have R look

Peter Krempa <pkrempa@redhat.com> writes: > On Tue, Jun 16, 2020 at 12:54:29 +0200, Milan Zamazal wrote: >> Hi, >> > >> I've found out that NVDIMM size and label size matter for regular >> (non-NV) DIMM hot plug. If the NVDIMM is not aligned correctly, the >> guest OS will not accept the hot plugged memory and will complain with >> messages

Please keep the list in cc. Sorry, it didn't work as expected. Maybe someone else have an appropriate solution. Best, Ulrik On Sa., 26. Aug. 2017, 12:57 niharika singhal <niharikasinghal1990 at gmail.com> wrote: > Hi > > Thanks for you mail, > I really appreciate your time on my problem > > I have posted this problem on > > >

Hi, I'm wondering if there's a method for doing any of these 1. Check what's the physical memory available. free -m shows ~768 mem but I was sure that I had 1G of memory in there. 2. I check the kernel and it seems like the 4G split is in effect so it should map / correctly recognise there's 1G of Mem there. Is there any way to check besides opening up the machine to look at it

Hello, I am facing a problem with optimization in R from 2-3 weeks. I have some Gaussian mixtures parameters and I want to find the maximum in that *Parameters are in the form * mean1 mean2 mean3 sigma1 sigma2 sigma3 c1 c2 c3 506.8644 672.8448 829.902 61.02859 9.149168 74.84682 0.1241933 0.6329082 0.2428986 I have used optima and optimx to find the