search for: dimms

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

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

...w 12, channel 1, label "": Corrected error (Branch=0, Channel 1), DRAM-Bank=2 RD RAS=8218 CAS=500, CE Err=0x10000, Syndrome=0x6cad8e02(Correctable Patrol Data ECC)) I see the Bank=2, so I assume that's the first riser board on the left; but I can't identify which of the four (?) DIMMs on it is the problem. I've been googling, and skimming useless manuals, and have just been trying to look under /sys/devices/system/edac/mc/mc0/. I see ce_count there showing thousands; but all of the ce_count files under csrow[0-7] show zero. Clues, anyone? mark

...ourth* 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's manufacturer. The board is a Tyan Tomcat i875p (S5102). Would it be possible that the DIMMs are being destroyed by some software component from the OS, perhaps the I2C management? The DIMMs do have EPROMS... Are they being incorrectly accessed by some software component and their program modified? Could this be the board's fault? And how? I don't know what to think of this, I ne...

...n 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 works for me with >> that QEMU machine just fine. > > I still could reproduce this issue with pc-i440fx-5.0 or pc. Did I miss anything? > Below I don't even see virtio_mem. I had to repair the image (filesystem fsck) because it was broken, can you try that as w...

...n 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 works for me with >> that QEMU machine just fine. > > I still could reproduce this issue with pc-i440fx-5.0 or pc. Did I miss anything? > Below I don't even see virtio_mem. I had to repair the image (filesystem fsck) because it was broken, can you try that as w...

...at QEMU has assigned. > Additionally, when adjusting maxMemory due to NVDIMM presence, should I > increase it by the specified NVDIMM <size> or a different value? IIRC, maxMemory has to allow for the sum of the basic RAM amount, plus RAM intended to be used for all possible future (NV)DIMMS that will be hotplugged. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

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

...- 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 works for me with >>>> that QEMU machine just fine. >>> >>> I still could reproduce this issue with pc-i440fx-5.0 or pc. Did I miss anything? >>> >> >> Below I don't even see virtio_mem. I had to repair the image (filesystem &gt...

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

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

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

In case we have to migrate a ballon page 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

In case we have to migrate a ballon page 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

I have recently upgraded to 2.6.18-194.3.1.el5 and within several days the machine crashed with the following error (repeating in mcelog): 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 Processor context corrupt MCA: MEMORY CONTROLLER AC_CHANNEL0_ERR

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