Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

edac-util(1) [centos man page]

EDAC-UTIL(1)						   EDAC error reporting utility 					      EDAC-UTIL(1)

NAME
edac-util - EDAC error reporting utility. SYNOPSIS
edac-util [OPTION]... DESCRIPTION
The edac-util program reads information from EDAC (Error Detection and Correction) drivers in the kernel, using files exported by these drivers in sysfs. With no options, edac-util will report any uncorrected error (UE) or corrected error (CE) information recorded by EDAC, along with any DIMM label information registered with EDAC. OPTIONS
-h, --help Display a summary of the command-line options. -q, --quiet Quiet mode. For some reports, edac-util will report corrected and uncorrected error counts for all MC, csrow, and channel combina- tions, even if the current count of errors is zero. The --quiet flag will suppress the display of any locations with zero errors, thus creating a more terse report. No output will be generated if there are zero total errors currently recorded by EDAC. Addition- ally, the use of --quiet will suppress all informational and debug messages, displaying only fatal errors. -v, --verbose Increase verbosity. Multiple -v's may be used. -s, --status Displays the current status of EDAC drivers. edac-util will report whether it detects that EDAC drivers are loaded, and the number of memory controllers (MCs) found in sysfs. In verbose mode, the MC id and name of each controller will also be printed. -r, --report=report,... Specify the report to generate. Currently, the available reports are default, simple, full, ue, and ce. These reports are detailed in the EDAC REPORTS section below. More than one report may be specified in a comma-separated list. EDAC REPORTS
default The default edac-util report is generated when the program is run without any options. If there are no errors logged by EDAC, this report will display "No errors to report." to stdout. Otherwise, error counts for each MC, csrow, channel combination with attrib- uted errors are displayed, along with corresponding DIMM labels, if these labels have been registered in sysfs. The default report will also display any errors that do not have any DIMM information. These errors occur when errors are reported in the memory controller overflow register, indicating that more than one error occurred during a given EDAC poll cycle. It is usu- ally obvious from which DIMM locations these errors were generated. simple The simple report reports total corrected and uncorrected errors for each MC detected on the system. It also displays a tally of total errors. With the --quiet option, only non-zero error counts are displayed. full The full report generates a line of output for every MC, csrow, channel combination found in EDAC sysfs. This includes counts of errors with no information ("noinfo" errors). Output is of the form: MC:(csrow|noinfo):(label|all):(UE|CE):count With the --quiet option, only non-zero error counts will be displayed. ue This report simply displays the total number of Uncorrected Errors (UEs) detected on the system. With the --quiet option, output will be suppressed unless there are 1 or more errors to report. ce This report simply displays the total number of Corrected Errors (CEs) detected on the system. With the --quiet option, output will be suppressed unless there are 1 or more errors to report. SEE ALSO
edac(3), edac-ctl(8) edac-utils-0.16-1 2009-01-30 EDAC-UTIL(1)

Check Out this Related Man Page

Tcl_BackgroundError(3)					      Tcl Library Procedures					    Tcl_BackgroundError(3)

__________________________________________________________________________________________________________________________________________________

NAME
Tcl_BackgroundError - report Tcl error that occurred in background processing SYNOPSIS
#include <tcl.h> Tcl_BackgroundError(interp) ARGUMENTS
Tcl_Interp *interp (in) Interpreter in which the error occurred. _________________________________________________________________ DESCRIPTION
This procedure is typically invoked when a Tcl error occurs during "background processing" such as executing an event handler. When such an error occurs, the error condition is reported to Tcl or to a widget or some other C code, and there is not usually any obvious way for that code to report the error to the user. In these cases the code calls Tcl_BackgroundError with an interp argument identifying the interpreter in which the error occurred. At the time Tcl_BackgroundError is invoked, the interpreter's result is expected to contain an error message. Tcl_BackgroundError will invoke the command registered in that interpreter to handle background errors by the interp bger- ror command. The registered handler command is meant to report the error in an application-specific fashion. The handler command receives two arguments, the result of the interp, and the return options of the interp at the time the error occurred. If the application registers no handler command, the default handler command will attempt to call bgerror to report the error. If an error condition arises while invoking the handler command, then Tcl_BackgroundError reports the error itself by printing a message on the standard error file. Tcl_BackgroundError does not invoke the handler command immediately because this could potentially interfere with scripts that are in process at the time the error occurred. Instead, it invokes the handler command later as an idle callback. It is possible for many background errors to accumulate before the handler command is invoked. When this happens, each of the errors is processed in order. However, if the handle command returns a break exception, then all remaining error reports for the interpreter are skipped. KEYWORDS
background, bgerror, error, interp Tcl 7.5 Tcl_BackgroundError(3)
Man Page