From patchwork Tue Jan 22 12:41:56 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Colin Ian King X-Patchwork-Id: 214538 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from chlorine.canonical.com (chlorine.canonical.com [91.189.94.204]) by ozlabs.org (Postfix) with ESMTP id 992D02C007B for ; Tue, 22 Jan 2013 23:42:00 +1100 (EST) Received: from localhost ([127.0.0.1] helo=chlorine.canonical.com) by chlorine.canonical.com with esmtp (Exim 4.71) (envelope-from ) id 1TxdAs-0006Qz-TQ; Tue, 22 Jan 2013 12:41:58 +0000 Received: from youngberry.canonical.com ([91.189.89.112]) by chlorine.canonical.com with esmtp (Exim 4.71) (envelope-from ) id 1TxdAr-0006Qo-7T for fwts-devel@lists.ubuntu.com; Tue, 22 Jan 2013 12:41:57 +0000 Received: from cpc3-craw6-2-0-cust180.croy.cable.virginmedia.com ([77.100.248.181] helo=localhost) by youngberry.canonical.com with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1TxdAr-0002F5-4v for fwts-devel@lists.ubuntu.com; Tue, 22 Jan 2013 12:41:57 +0000 From: Colin King To: fwts-devel@lists.ubuntu.com Subject: [PATCH] data: klog.json: Handle SystemIO conflict messages Date: Tue, 22 Jan 2013 12:41:56 +0000 Message-Id: <1358858516-24950-1-git-send-email-colin.king@canonical.com> X-Mailer: git-send-email 1.8.0 X-BeenThere: fwts-devel@lists.ubuntu.com X-Mailman-Version: 2.1.13 Precedence: list List-Id: Firmware Test Suite Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Sender: fwts-devel-bounces@lists.ubuntu.com Errors-To: fwts-devel-bounces@lists.ubuntu.com From: Colin Ian King Add in some helpful advice for SystemIO conflict messages. This ACPI message was first seen in bug report LP:#1102370, so it seems sensible to make fwts diagnose the problem rather than giving some less than helpful error report. Signed-off-by: Colin Ian King Acked-by: Keng-Yu Lin Acked-by: Alex Hung --- data/klog.json | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/data/klog.json b/data/klog.json index d526979..1fc48be 100644 --- a/data/klog.json +++ b/data/klog.json @@ -75,6 +75,14 @@ }, { "compare_mode": "regex", + "log_level": "LOG_LEVEL_LOW", + "tag": "FWTS_TAG_ACPI", + "pattern": "0x.*-0x.* SystemIO conflicts with", + "advice": "A resource conflict between an ACPI OperationRegion and a native driver has been detected. By default the kernel will use a strict policy and will not allow this region to conflict and -EBUSY will be returned to the caller that was trying to allocate the already claimed region. If an ACPI driver is available for this device then this should be used instead of a native driver, so disabling the native driver may help. One can specify kernel boot paramater acpi_enforce_resources=lax to disable these checks but it may lead to random problems and system instability. Alternatively, one can specify acpi_enforce_resources=no and ACPI Operation Region resources will not be registered.", + "label": "KlogAcpiSystemIOConflict", + }, + { + "compare_mode": "regex", "log_level": "LOG_LEVEL_MEDIUM", "tag": "FWTS_TAG_BIOS", "pattern": "device .* has invalid IRQ.*check vendor BIOS",