@@ -4544,6 +4544,13 @@
"advice": "ACPI failed to evaluate a processor _UID object (as declared in a Device statement). ACPI could not gather information on a CPU which will lead to it not being used.",
"label": "KlogAcpiProcessorEvalFailed"
},
+ {
+ "compare_mode": "string",
+ "log_level": "LOG_LEVEL_HIGH",
+ "pattern": "Failed to get unique processor _UID",
+ "advice": "ACPI failed to get a processor unigue processor _UID. This normally occurs because of buggy firmware that implemented duplicate UID for processors.",
+ "label": "KlogAcpiDuplicateProcessorUID"
+ },
{
"compare_mode": "string",
"log_level": "LOG_LEVEL_MEDIUM",
@@ -5314,6 +5321,13 @@
"advice": "An attempt to add a processor to the system failed in acpi_processor_add(), the processor driver's .probe failed calling device_attach(). The CPU cannot be added to the system under ACPI control.",
"label": "KlogAcpiProcessorNotAttached"
},
+ {
+ "compare_mode": "string",
+ "log_level": "LOG_LEVEL_HIGH",
+ "pattern": "ACPI: Failed to claim processor _CST control",
+ "advice": "An attempt to request _CST control from SMI command base on FADT but fail.",
+ "label": "KlogAcpiProcessorNotAttached"
+ },
{
"compare_mode": "string",
"log_level": "LOG_LEVEL_HIGH",
These messages are specific to the ACPI processor driver. Signed-off-by: Ivan Hu <ivan.hu@canonical.com> --- data/klog.json | 14 ++++++++++++++ 1 file changed, 14 insertions(+)