search for: dimm

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 addres...

..., 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 does this map to the on board labels DIMM 1A DIMM 1B DIMM 2A DIMM 2B Am I correct in assuming csrow 3 is DIMM 2B? Also I have just discovered that both the OS drives sda and sdb have huge number of errors shown on the SMART records - can this relate to the memory errors?? - I am just really surprised to have two drives show almost ident...

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: EDAC MC0: CE row 12, channel 1, label "": Corrected error (Branch=0, Channel 1), DRAM-Bank=2 RD RAS=8218 CAS=500, CE Err=0...

...ng CentOS 5 on a small server and I am having very strange memory malfunctions. The computer runs perfectly with no problems whatsoever. From time to time, after a soft reboot, the computer emmits beeps corresponding to a memory fault. It never reboots again until I find and remove a now defective DIMM. That DIMM can never be used again because it is out of order. This just happened for the *fourth* time and is costing me a lot of hassle and perhaps expense if the manufacturer does not replace the DIMM freely. The memory is DDR400 ECC from Kingston and of the type recommended by the motherboard...

...> ??? >> >> On 14.05.20 08:44, teawater wrote: >>> Hi David, >>> >>> I got a kernel warning with v2 and v3. >> >> Hi Hui, >> >> thanks for playing with the latest versions. Surprisingly, I can >> reproduce even by hotplugging a DIMM instead as well - that's good, so >> it's not related to virtio-mem, lol. Seems to be some QEMU setup issue >> with older machine types. >> >> Can you switch to a newer qemu machine version, especially >> pc-i440fx-5.0? Both, hotplugging DIMMs and virtio-mem wo...

...> ??? >> >> On 14.05.20 08:44, teawater wrote: >>> Hi David, >>> >>> I got a kernel warning with v2 and v3. >> >> Hi Hui, >> >> thanks for playing with the latest versions. Surprisingly, I can >> reproduce even by hotplugging a DIMM instead as well - that's good, so >> it's not related to virtio-mem, lol. Seems to be some QEMU setup issue >> with older machine types. >> >> Can you switch to a newer qemu machine version, especially >> pc-i440fx-5.0? Both, hotplugging DIMMs and virtio-mem wo...

On Tue, Jun 16, 2020 at 12:54:29PM +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 such as > > Block size [0x8000000] unaligned hotplug range: start 0x225000000, size 0x1...

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 such as >> >> Block size [0x8000000] unaligned hotplug range: start 0...

...t;>>>> Hi David, >>>>> >>>>> I got a kernel warning with v2 and v3. >>>> >>>> Hi Hui, >>>> >>>> thanks for playing with the latest versions. Surprisingly, I can >>>> reproduce even by hotplugging a DIMM instead as well - that's good, so >>>> it's not related to virtio-mem, lol. Seems to be some QEMU setup issue >>>> with older machine types. >>>> >>>> Can you switch to a newer qemu machine version, especially >>>> pc-i440fx-5.0? B...

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 such as > > Block size [0x8000000] unaligned hotplug range: start 0x225000000, size 0x1...

I am trying to get the temperature of a Poweredge 2850 with CentOS 6.3 on it. Has anybody on this list done this successfully? Thanks -Surya PS: Apologies for cross posting if you are on the Poweredge list. -- Surya Saha Department of Plant Pathology and Plant-Microbe Biology Cornell University, NY, USA http://www.linkedin.com/in/suryasaha

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

Xen Users, Has anyone on the list been able to run Xen 4 on an Intel DX58S02 board? Sincerely, John McDermott ---- What is the formal meaning of the one-line program #include "/dev/tty" J.P. McDermott building 12 Code 5542 john.mcdermott@nrl.navy.mil Naval Research Laboratory voice: +1 202.404.8301 Washington, DC 20375, US fax: +1 202.404.7942

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

...gt; >> >> You know what this justification is rubbish, and I have previously >> explained why it is rubbish. > > Actually, no, I don't think it is rubbish. See patch #3 and the cover > letter why this is the right thing to do *for special memory*, *not > ordinary DIMMs*. > > And to be quite honest, I think your response is a little harsh. I don't > recall you replying to my virtio-mem-related comments. > >> >> Nacked-by: "Eric W. Biederman" <ebiederm at xmission.com> >> >> This needs to be based on weathe...

...gt; >> >> You know what this justification is rubbish, and I have previously >> explained why it is rubbish. > > Actually, no, I don't think it is rubbish. See patch #3 and the cover > letter why this is the right thing to do *for special memory*, *not > ordinary DIMMs*. > > And to be quite honest, I think your response is a little harsh. I don't > recall you replying to my virtio-mem-related comments. > >> >> Nacked-by: "Eric W. Biederman" <ebiederm at xmission.com> >> >> This needs to be based on weathe...

...ge to a newpage of another zone, the managed page count of both zones is wrong. Paired with memory offlining (which will adjust the managed page count), we can trigger kernel crashes and all kinds of different symptoms. One way to reproduce: 1. Start a QEMU guest with 4GB, no NUMA 2. Hotplug a 1GB DIMM and only the memory to ZONE_NORMAL 3. Inflate the balloon to 1GB 4. Unplug the DIMM (be quick, otherwise unmovable data ends up on it) 5. Observe /proc/zoneinfo Node 0, zone Normal pages free 16810 min 24848885473806 low 18471592959183339 high...

...ge to a newpage of another zone, the managed page count of both zones is wrong. Paired with memory offlining (which will adjust the managed page count), we can trigger kernel crashes and all kinds of different symptoms. One way to reproduce: 1. Start a QEMU guest with 4GB, no NUMA 2. Hotplug a 1GB DIMM and only the memory to ZONE_NORMAL 3. Inflate the balloon to 1GB 4. Unplug the DIMM (be quick, otherwise unmovable data ends up on it) 5. Observe /proc/zoneinfo Node 0, zone Normal pages free 16810 min 24848885473806 low 18471592959183339 high...

...atus: MCi status: Error overflow Uncorrected error MCi_MISC register valid Processor context corrupt MCA: MEMORY CONTROLLER AC_CHANNEL0_ERR Transaction: Address/Command error Memory address parity error Memory corrected error count (CORE_ERR_CNT): 911 Memory transaction Tracker ID (RTId): 41 Memory DIMM ID of error: 0 Memory channel ID of error: 0 Memory ECC syndrome: 0 STATUS ea10e3c0008000b0 MCGSTATUS 0 MCE 0 HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 2 BANK 8 MISC 41 MCG status: MCi status: Error overflow Uncorrected error MCi_MISC register valid P...

I am planning to build a server based on the SuperMicro X7DBE+-O motherboard. This server will have two dual-core Xeon processors and a 3ware 9550SX raid card. Has anyone built a server based on this motherboard? Are there any issues with the smp/dual-core support in CentOS4 that might cause problems? I appreciate any input. I'm just looking to find out about any possible problems before