diff mbox

[V2] klog.json: add an ACPI warning message "SysmtemMemory conflicts

Message ID 1494534805-5112-1-git-send-email-alex.hung@canonical.com
State Accepted
Headers show

Commit Message

Alex Hung May 11, 2017, 8:33 p.m. UTC
Signed-off-by: Alex Hung <alex.hung@canonical.com>
---
 data/klog.json | 7 +++++++
 1 file changed, 7 insertions(+)

Comments

Colin Ian King May 11, 2017, 9:24 p.m. UTC | #1
On 11/05/17 21:33, Alex Hung wrote:
> Signed-off-by: Alex Hung <alex.hung@canonical.com>
> ---
>  data/klog.json | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/data/klog.json b/data/klog.json
> index 7104f2b..2cb0008 100644
> --- a/data/klog.json
> +++ b/data/klog.json
> @@ -5610,6 +5610,13 @@ atform Communications Channel Table (PCCT) and find the PCC subspace communicati
>     "label": "KlogAcpiInvalidThrottlingState"
>    },
>    {
> +   "compare_mode": "regex",
> +   "log_level": "LOG_LEVEL_LOW",
> +   "pattern": "ACPI Warning: SystemMemory range 0x.*-0x.* 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 parameter 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": "KlogAcpiSystemMemoryConflict"
> +  },
> +  {
>     "compare_mode": "string",
>     "log_level": "LOG_LEVEL_HIGH",
>     "pattern": "ACPI Warning",
> 
Thanks Alex

Acked-by: Colin Ian King <colin.king@canonical.com>
Ivan Hu May 23, 2017, 7:26 a.m. UTC | #2
On 05/12/2017 04:33 AM, Alex Hung wrote:
> Signed-off-by: Alex Hung <alex.hung@canonical.com>
> ---
>   data/klog.json | 7 +++++++
>   1 file changed, 7 insertions(+)
>
> diff --git a/data/klog.json b/data/klog.json
> index 7104f2b..2cb0008 100644
> --- a/data/klog.json
> +++ b/data/klog.json
> @@ -5610,6 +5610,13 @@ atform Communications Channel Table (PCCT) and find the PCC subspace communicati
>      "label": "KlogAcpiInvalidThrottlingState"
>     },
>     {
> +   "compare_mode": "regex",
> +   "log_level": "LOG_LEVEL_LOW",
> +   "pattern": "ACPI Warning: SystemMemory range 0x.*-0x.* 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 parameter 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": "KlogAcpiSystemMemoryConflict"
> +  },
> +  {
>      "compare_mode": "string",
>      "log_level": "LOG_LEVEL_HIGH",
>      "pattern": "ACPI Warning",

Acked-by: Ivan Hu <ivan.hu@canonical.com>
diff mbox

Patch

diff --git a/data/klog.json b/data/klog.json
index 7104f2b..2cb0008 100644
--- a/data/klog.json
+++ b/data/klog.json
@@ -5610,6 +5610,13 @@  atform Communications Channel Table (PCCT) and find the PCC subspace communicati
    "label": "KlogAcpiInvalidThrottlingState"
   },
   {
+   "compare_mode": "regex",
+   "log_level": "LOG_LEVEL_LOW",
+   "pattern": "ACPI Warning: SystemMemory range 0x.*-0x.* 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 parameter 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": "KlogAcpiSystemMemoryConflict"
+  },
+  {
    "compare_mode": "string",
    "log_level": "LOG_LEVEL_HIGH",
    "pattern": "ACPI Warning",