similar to: Bug#810964: Same problem with Xen 4.6

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

>>> 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 with single 6120 (dual memory controller) and twin 6344 (2x dual >

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

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

On Mon, May 15, 2017 at 02:02:53AM -0600, Jan Beulich wrote: > >>> On 14.05.17 at 00:36, <ehem+debian at m5p.com> wrote: > > 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

>>> On 22.01.16 at 10:09, <pgadmin at pse-consulting.de> wrote: > When booting with Xen 4.4.1: > > 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. I wonder how valid his message is. We actually write this MSR with all ones during boot. However, considering involved functions

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

Processing commands for control at bugs.debian.org: > forwarded 810964 http://lists.xen.org/archives/html/xen-devel/2016-01/msg02479.html Bug #810964 [xen-hypervisor-4.4-amd64] only partial EDAC information with Xen Set Bug forwarded-to-address to 'http://lists.xen.org/archives/html/xen-devel/2016-01/msg02479.html'. > thanks Stopping processing here. Please contact me if you need

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

Hello, I upgraded to CentOS 5.1 and everything went smoothly (Thanks for the awesome work!). But after rebooting, I get the following error: EDAC MC: Ver: 2.0.1 Nov 30 2007 EDAC e7xxx: error reporting device not found:vendor 8086 device 0x2541 (broken BIOS?) I found http://edacbugs.buttersideup.com/show_bug.cgi?id=21 with google but no solution. Is it safe to ignore the error or remove

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #8 from Philippe Condé <conde.philippe at skynet.be> --- Hello, I desactivated kscreenlocker which resolve the reactivate problem. But the problem of corrupt screen when starting different programs remains and is worst since the last zypper dup. I found this error still related to nouveau when the two screen got corrupted ov

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

On Mon, Sep 11, 2017 at 04:27:30PM +0000, Seth Tanner wrote: > Rich, > Here you go > I also noticed that if I use the direct backend rather than libvirt, the conversion gets farther, but still does not complete, when pulling directly from vSphere. please let me know if you would like the output of direct as well. > starting version 233 > + udevadm trigger > + udevadm settle

This morning between 07:10 or so and 08:10 I discovered that my PC had shut itself off. I thought it was due to a power failure becuase I never turn it off without a good reason, and it had been running (and playing sounds) until it wasn't. My roommate/landlord tells me that the only anomaly he observed was that our router had lost its internet connection (via a cable modem, which was still

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:

Package: xen-utils-4.6 Version: 4.6.0-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these

I just migrated a W2K3 Server to a Xen HVM domain, using the gplpv 0.10.69 drivers. Now ping shows strange results: Pinging 127.0.0.1 with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time=23538ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time=-23538ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Same result with external

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

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Tags: squeeze The host runs (at the time of testing) a single linux-x86 domu (128MB, 1VCPU). When issuing a reboot, everything looks as expected: - domu is saved - xend is stopped - drbd stopped - lvms unmounted - md0..4 stopped and the message "rebooting now" appears, but nothing happens until "INFO: task xenwatch is

New kernel install spits out a lot of warnings about unknown symbols in the edac drivers: Installing: kernel i586 2.6.9-34.EL update 10 M [ ... ] Installing: kernel ####################### [10/19] WARNING: /lib/modules/2.6.9-34.EL/kernel/drivers/edac/i82860_edac.ko needs unknown symbol edac_mc_del_mc WARNING: