From: Tracy Smith <tlsmith3777@gmail.com>
To: york.sun@nxp.com
Cc: linux-edac@vger.kernel.org, util-linux@vger.kernel.org
Subject: Re: edac driver injection of uncorrected errors & utils
Date: Wed, 28 Nov 2018 13:11:23 -0600 [thread overview]
Message-ID: <CAChUvXN8rZqxBaV2qbdR8uymsmZAk_Jnc2kxSUf+kBf76QHV9A@mail.gmail.com> (raw)
In-Reply-To: <AM0PR04MB3971768EA5D50D7045B462619AD10@AM0PR04MB3971.eurprd04.prod.outlook.com>
Thanks York. Why will injecting multi-bit errors crash linux? Is this
the case only for layerscape? Is there a way to harden against this?
On Wed, Nov 28, 2018 at 1:06 PM York Sun <york.sun@nxp.com> wrote:
>
> Tracy,
>
> You can inject multiple-bit errors. You will crash the system for doing
> that. I can't comment on edac-util.
>
> York
>
>
> On 11/28/18 12:49 PM, Tracy Smith wrote:
> > Can I inject a uncorrected error or only corrected errors using the
> > layerscape edac driver injection via sysfs?
> >
> > Is this the expected output for the edac-util on layerscape when
> > injecting errors?
> >
> > root@ls1043ardb:~# edac-util -v
> > mc0: 0 Uncorrected Errors with no DIMM info
> > mc0: 0 Corrected Errors with no DIMM info
> > mc0: csrow0: 0 Uncorrected Errors
> > mc0: csrow0: mc#0csrow#0channel#0: 643 Corrected Errors
> >
> > root@ls1043ardb:~# edac-util -vs
> > edac-util: EDAC drivers are loaded. 1 MC detected:
> > mc0:fsl_mc_err
> >
> > root@ls1043ardb:~# edac-util
> > mc0: csrow0: mc#0csrow#0channel#0: 2700 Corrected Errors
> >
> > Does edac-ctl function on ARM based platforms or only on x86 and why
> > might it show 0MB for the memory layout for DDR4 as below?
> >
> > /run/media/nvme0n1p1/tls/neo_mcu-kernel/drivers/edac-utils# edac-ctl
> > --layoutreadline() on closed filehandle IN at /usr/sbin/edac-ctl line
> > 514.
> > Use of uninitialized value $size in sprintf at /usr/sbin/edac-ctl line 533.
> > Use of uninitialized value $size in sprintf at /usr/sbin/edac-ctl line 533.
> > Use of uninitialized value $size in sprintf at /usr/sbin/edac-ctl line 533.
> > Use of uninitialized value $size in sprintf at /usr/sbin/edac-ctl line 533.
> > +-----------------------------------------------+
> > | mc0 |
> > | csrow0 | csrow1 | csrow2 | csrow3 |
> > ----------+-----------------------------------------------+
> > channel0: | 0 MB | 0 MB | 0 MB | 0 MB |
> > ----------+-----------------------------------------------+
> >
>
--
Confidentiality notice: This e-mail message, including any
attachments, may contain legally privileged and/or confidential
information. If you are not the intended recipient(s), please
immediately notify the sender and delete this e-mail message.
next prev parent reply other threads:[~2018-11-28 19:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BYAPR02MB431115EC4735AE5B7E29F2CEF6DC0@BYAPR02MB4311.namprd02.prod.outlook.com>
[not found] ` <BYAPR02MB43110062F32BFDEA712AB371F6DC0@BYAPR02MB4311.namprd02.prod.outlook.com>
[not found] ` <CAChUvXMp6S6MBY_LmrfgdPcctQw70FoyxbiHeFqK+5fQx5omCw@mail.gmail.com>
2018-11-16 17:07 ` FW: edac driver initialization, interrupt, & debug Tracy Smith
2018-11-17 14:05 ` Borislav Petkov
2018-11-17 23:22 ` Tracy Smith
2018-11-18 1:05 ` Steve Inkpen
2018-11-19 16:37 ` Tracy Smith
2018-11-19 16:48 ` York Sun
2018-11-21 17:01 ` Tracy Smith
2018-11-21 22:02 ` Tracy Smith
2018-11-28 18:48 ` edac driver injection of uncorrected errors & utils Tracy Smith
2018-11-28 19:06 ` York Sun
2018-11-28 19:11 ` Tracy Smith [this message]
2018-11-28 19:24 ` York Sun
2018-11-28 22:14 ` Tracy Smith
2018-11-28 23:44 ` Borislav Petkov
2018-12-05 16:37 ` Tracy Smith
2018-12-05 17:12 ` Borislav Petkov
2018-12-05 17:59 ` York Sun
2018-12-05 21:59 ` Patrol scrub questions Tracy Smith
2018-12-05 22:12 ` York Sun
2018-12-05 22:53 ` Layerscape behavior when a UE is detected Tracy Smith
2018-12-05 22:57 ` York Sun
2018-12-05 23:41 ` Layerscape UE detected and no EDAC panic Tracy Smith
2018-11-19 16:24 ` FW: edac driver initialization, interrupt, & debug York Sun
2018-11-19 15:55 ` York Sun
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=CAChUvXN8rZqxBaV2qbdR8uymsmZAk_Jnc2kxSUf+kBf76QHV9A@mail.gmail.com \
--to=tlsmith3777@gmail.com \
--cc=linux-edac@vger.kernel.org \
--cc=util-linux@vger.kernel.org \
--cc=york.sun@nxp.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).