From: "Jan Beulich" <JBeulich@suse.com>
To: Andreas Pflug <andreas.pflug@web.de>
Cc: 810964@bugs.debian.org, xen-devel@lists.xen.org
Subject: Re: [BUG] EDAC infomation partially missing
Date: Thu, 21 Jan 2016 09:41:29 -0700 [thread overview]
Message-ID: <56A1184902000078000C9B3D@prv-mh.provo.novell.com> (raw)
In-Reply-To: <569FA160.6070308@web.de>
>>> On 20.01.16 at 16:01, <andreas.pflug@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
> MC), other dual-module CPUs might be affected too.
>
> Booting plain Linux (3.2, 3.16, 4.1, 4.3), all memory controllers are
> listed under /sys/devices/system/edac/mc as expected. Same happens, when
> Xen 4.1 is used: all MCs present.
>
> Starting with Xen 4.4 (Debian Jessie), only mc1 (on the single CPU
> machine) or mc2/mc3 (dual CPU machine) are present, although the full
> system memory is accessible. Checked versions were 4.1.4 (Debian
> Wheezy), 4.4.1 (Jessie) and 4.6.0 (Sid)
As already indicated by Ian in that bug, you should supply us with
full kernel and hypervisor logs for both the good and bad cases
(ideally with the same kernel version use in both runs, so that we
can exclude kernel behavior differences).
Jan
next parent reply other threads:[~2016-01-21 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <569FA160.6070308@web.de>
2016-01-21 16:41 ` Jan Beulich [this message]
2016-01-22 9:09 ` [BUG] EDAC infomation partially missing Andreas Pflug
2016-01-22 10:40 ` Jan Beulich
2016-01-22 11:33 ` Andreas Pflug
[not found] <20170513223656.GA40303@scollay.m5p.com>
2017-05-15 8:02 ` Jan Beulich
2017-05-16 3:47 ` Elliott Mitchell
2017-05-16 9:54 ` Jan Beulich
2017-05-16 10:08 ` Andrew Cooper
2017-05-16 18:02 ` Elliott Mitchell
2017-05-13 22:36 Elliott Mitchell
-- strict thread matches above, loose matches on Subject: below --
2016-01-20 15:01 Andreas Pflug
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56A1184902000078000C9B3D@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=810964@bugs.debian.org \
--cc=andreas.pflug@web.de \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.