From patchwork Tue Nov 20 11:28:04 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [8/8] data: klog.json: ACPICA ACPI_ERROR messages, utmutex.c From: Colin King X-Patchwork-Id: 200305 Message-Id: <1353410884-4438-9-git-send-email-colin.king@canonical.com> To: fwts-devel@lists.ubuntu.com Date: Tue, 20 Nov 2012 11:28:04 +0000 From: Colin Ian King ACPICA ACPI_ERROR messages from utmutex.c Signed-off-by: Colin Ian King Acked-by: Keng-Yu Lin Acked-by: Ivan Hu --- data/klog.json | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/data/klog.json b/data/klog.json index a029b5e..bf4d084 100644 --- a/data/klog.json +++ b/data/klog.json @@ -77,6 +77,22 @@ "firmware_error_warning_patterns": [ { + "compare_mode": "regex", + "log_level": "LOG_LEVEL_HIGH", + "tag": "FWTS_TAG_ACPI", + "pattern": "Mutex .* is not acquired, cannot release", + "advice": "An attempt to release (unlock) an ACPI related mutex has occurred. This mutex could not be released. This is most probably a bug in the AML code where a Release opcode has been executed that does not match up with an earlier corresponding Mutex opcode. It may also be a bug in the ACPI driver, but this is less likely.", + "label": "KlogAcpiMutexReleaseError" + }, + { + "compare_mode": "regex", + "log_level": "LOG_LEVEL_HIGH", + "tag": "FWTS_TAG_ACPI", + "pattern": "Thread .* could not acquire Mutex", + "advice": "A mutex could not be acquired (locked) and the ACPI driver has flagged this up as an exception error. If this occurs when executing a AML Mutex opcode there could be race condition errors if the AML is not checking the return from the Mutex operation and a lot of firmware does omit this check.", + "label": "KlogAcpiMutexAcquireError" + }, + { "compare_mode": "string", "log_level": "LOG_LEVEL_CRITICAL", "tag": "FWTS_TAG_ACPI",