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@xxxxxxx> 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.
