diff options
Diffstat (limited to 'static/netbsd/man4/apei.4 4.html')
| -rw-r--r-- | static/netbsd/man4/apei.4 4.html | 107 |
1 files changed, 0 insertions, 107 deletions
diff --git a/static/netbsd/man4/apei.4 4.html b/static/netbsd/man4/apei.4 4.html deleted file mode 100644 index 039308a8..00000000 --- a/static/netbsd/man4/apei.4 4.html +++ /dev/null @@ -1,107 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">APEI(4)</td> - <td class="head-vol">Device Drivers Manual</td> - <td class="head-rtitle">APEI(4)</td> - </tr> -</table> -<div class="manual-text"> -<section class="Sh"> -<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1> -<p class="Pp"><code class="Nm">apei</code> — <span class="Nd">ACPI - Platform Error Interfaces</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1> -<p class="Pp"><code class="Cd">apei* at apeibus?</code></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp"><code class="Nm">apei</code> reports hardware errors discovered - through APEI, the ACPI Platform Error Interfaces.</p> -<p class="Pp"><code class="Nm">apei</code> also supports injecting errors.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<p class="Pp">When the hardware detects an error and reports it to - <code class="Nm">apei</code>, it will print information about the error to - the console.</p> -<p class="Pp">Example of a correctable memory error, automatically corrected by - the system, with no further intervention needed:</p> -<div class="Bd Pp Li"> -<pre>apei0: error source 1 reported hardware error: severity=corrected nentries=1 status=0x12<CE,GEDE_COUNT=0x1> -apei0: error source 1 entry 0: SectionType={0xa5bc1114,0x6f64,0x4ede,0xb8b8,{0x3e,0x83,0xed,0x7c,0x83,0xb1}} (memory error) -apei0: error source 1 entry 0: ErrorSeverity=2 (corrected) -apei0: error source 1 entry 0: Revision=0x201 -apei0: error source 1 entry 0: Flags=0x1<PRIMARY> -apei0: error source 1 entry 0: FruText=CorrectedErr -apei0: error source 1 entry 0: MemoryErrorType=8 (PARITY_ERROR) - -Example of a fatal uncorrectable memory error: -</pre> -<div class="Bd Pp Li"> -apei0: error source 0 reported hardware error: severity=fatal nentries=1 - status=0x11<UE,GEDE_COUNT=0x1> -apei0: error source 0 entry 0: - SectionType={0xa5bc1114,0x6f64,0x4ede,0xb8b8,{0x3e,0x83,0xed,0x7c,0x83,0xb1}} - (memory error) -apei0: error source 0 entry 0: ErrorSeverity=1 (fatal) -apei0: error source 0 entry 0: Revision=0x201 -apei0: error source 0 entry 0: Flags=0x1<PRIMARY> -apei0: error source 0 entry 0: FruText=UncorrectedErr -apei0: error source 0 entry 0: ErrorStatus=0x400<ErrorType=0x4=ERR_MEM> -apei0: error source 0 entry 0: Node=0x0 -apei0: error source 0 entry 0: Module=0x0 -apei0: error source 0 entry 0: Device=0x0 -panic: fatal hardware error</div> - -Details of the hardware error sources can be dumped with -<a class="Xr">acpidump(8)</a>.</div> -</section> -<section class="Sh"> -<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE - ALSO</a></h1> -<p class="Pp"><a class="Xr">acpi(4)</a>, <a class="Xr">acpihed(4)</a>, - <a class="Xr">acpidump(8)</a></p> -<p class="Pp"><cite class="Rs"><i class="RsB">ACPI Specification 6.5</i>, - <a class="RsU" href="https://uefi.org/specs/ACPI/6.5/18_Platform_Error_Interfaces.html">https://uefi.org/specs/ACPI/6.5/18_Platform_Error_Interfaces.html</a>, - <span class="RsO">Chapter 18: ACPI Platform Error Interfaces - (APEI)</span>.</cite></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">apei</code> driver first appeared in - <span class="Ux">NetBSD 10.1</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp">The <code class="Nm">apei</code> driver was written by - <span class="An">Taylor R Campbell</span> - <<a class="Mt" href="mailto:riastradh@NetBSD.org">riastradh@NetBSD.org</a>>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">No sysctl interface to read BERT after boot.</p> -<p class="Pp">No simple sysctl interface to inject errors with EINJ, or any way - to inject errors at physical addresses in pages allocated for testing. - Perhaps there should be a separate kernel module for that.</p> -<p class="Pp">Nothing reads, writes, or clears ERST. - <span class="Ux">NetBSD</span> could use it to store dmesg or other - diagnostic information on panic.</p> -<p class="Pp">Many hardware error source types in the HEST are missing, such as - PCIe errors.</p> -<p class="Pp"><code class="Nm">apei</code> is not wired to any machine-dependent - machine check exception notifications.</p> -<p class="Pp">No formal log format or sysctl/device interface that programs can - reliably act on.</p> -<p class="Pp"><span class="Ux">NetBSD</span> makes no attempt to recover from - uncorrectable but recoverable errors, such as discarding a clean cached page - where an uncorrectable memory error has occurred.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">March 18, 2024</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |