CONFIG_EDAC_GHES: Output ACPI APEI/GHES BIOS detected errors via EDAC

General informations

The Linux kernel configuration item CONFIG_EDAC_GHES has multiple definitions:

Output ACPI APEI/GHES BIOS detected errors via EDAC found in drivers/edac/Kconfig

The configuration item CONFIG_EDAC_GHES:

• prompt: Output ACPI APEI/GHES BIOS detected errors via EDAC
• type: tristate
• depends on: CONFIG_ACPI_APEI_GHES
• defined in drivers/edac/Kconfig
• found in Linux kernels: 6.2–6.12
• modules built: ghes_edac

Help text

Not all machines support hardware-driven error report. Some of those provide a BIOS-driven error report mechanism via ACPI, using the APEI/GHES driver. By enabling this option, the error reports provided by GHES are sent to userspace via the EDAC API.

When this option is enabled, it will disable the hardware-driven mechanisms, if a GHES BIOS is detected, entering into the "Firmware First" mode.

It should be noticed that keeping both GHES and a hardware-driven error mechanism won't work well, as BIOS will race with OS, while reading the error registers. So, if you want to not use "Firmware first" GHES error mechanism, you should disable GHES either at compilation time or by passing "ghes.disable=1" Kernel parameter at boot time.

In doubt, say 'Y'.

Output ACPI APEI/GHES BIOS detected errors via EDAC found in drivers/edac/Kconfig

The configuration item CONFIG_EDAC_GHES:

• prompt: Output ACPI APEI/GHES BIOS detected errors via EDAC
• type: bool
• depends on: CONFIG_ACPI_APEI_GHES && ( CONFIG_EDAC = CONFIG_y )
• defined in drivers/edac/Kconfig
• found in Linux kernels: 3.9–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.1, 6.1+HEAD
• modules built: ghes_edac

Help text

Not all machines support hardware-driven error report. Some of those provide a BIOS-driven error report mechanism via ACPI, using the APEI/GHES driver. By enabling this option, the error reports provided by GHES are sent to userspace via the EDAC API.

When this option is enabled, it will disable the hardware-driven mechanisms, if a GHES BIOS is detected, entering into the "Firmware First" mode.

It should be noticed that keeping both GHES and a hardware-driven error mechanism won't work well, as BIOS will race with OS, while reading the error registers. So, if you want to not use "Firmware first" GHES error mechanism, you should disable GHES either at compilation time or by passing "ghes.disable=1" Kernel parameter at boot time.

In doubt, say 'Y'.

Hardware

LKDDb

Raw data from LKDDb:

• lkddb module ghes_edac CONFIG_EDAC_GHES : drivers/edac/Kconfig : "Output ACPI APEI/GHES BIOS detected errors via EDAC" # in 6.2–6.12

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: