From: "Jan Beulich" <JBeulich@suse.com>
To: Elliott Mitchell <ehem+debian@m5p.com>
Cc: 810964@bugs.debian.org, xen-devel@lists.xen.org
Subject: Re: [BUG] EDAC infomation partially missing
Date: Mon, 15 May 2017 02:02:53 -0600 [thread overview]
Message-ID: <59197CCD0200007800159AF2@prv-mh.provo.novell.com> (raw)
In-Reply-To: <20170513223656.GA40303@scollay.m5p.com>
>>> On 14.05.17 at 00:36, <ehem+debian@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 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 capability, module will not
> load.
> 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 capability, module will not
> load.
Afaict the driver as is simply can't work in a Xen Dom0; it needs
enabling (read: para-virtualizing). I'm actually glad to see it doesn't
load (the worse alternative would be for it to load and then do the
wrong thing or give you a false sense of safety of your data).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next parent reply other threads:[~2017-05-15 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170513223656.GA40303@scollay.m5p.com>
2017-05-15 8:02 ` Jan Beulich [this message]
2017-05-16 3:47 ` [BUG] EDAC infomation partially missing 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
[not found] <569FA160.6070308@web.de>
2016-01-21 16:41 ` Jan Beulich
2016-01-22 9:09 ` Andreas Pflug
2016-01-22 10:40 ` Jan Beulich
2016-01-22 11:33 ` Andreas Pflug
-- 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=59197CCD0200007800159AF2@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=810964@bugs.debian.org \
--cc=ehem+debian@m5p.com \
--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.