Patchwork data: klog.json: Add some more advice for the now common lpc_ich warnings

login
register
mail settings
Submitter Colin King
Date June 5, 2013, 1:23 p.m.
Message ID <1370438590-4155-1-git-send-email-colin.king@canonical.com>
Download mbox | patch
Permalink /patch/249054/
State Accepted
Headers show

Comments

Colin King - June 5, 2013, 1:23 p.m.
From: Colin Ian King <colin.king@canonical.com>

These warnings are occuring frequently nowadays, and for most cases they
are not a real issue at all. Add some more specific advice to put the warning
into context.

Signed-off-by: Colin Ian King <colin.king@canonical.com>
---
 data/klog.json | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)
Alex Hung - June 6, 2013, 1:17 a.m.
On 06/05/2013 09:23 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> These warnings are occuring frequently nowadays, and for most cases they
> are not a real issue at all. Add some more specific advice to put the warning
> into context.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>   data/klog.json | 18 +++++++++++++++++-
>   1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/data/klog.json b/data/klog.json
> index 9727894..2d297b2 100644
> --- a/data/klog.json
> +++ b/data/klog.json
> @@ -1362,11 +1362,27 @@
>      "label": "KlogACPIPrwEvalError"
>     },
>     {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_LOW",
> +   "tag": "FWTS_TAG_ACPI",
> +   "pattern": "lpc_ich: Resource conflict(s) found affecting iTCO_wdt",
> +   "advice": "A resource conflict has occurred between ACPI OperationRegions and the same I/O region used by the lpc_ich driver for the Intel TCO (Total Cost of Ownership) timer (iTCO_wdt, this is a watchdog timer that will reboot the machine after its second expiration). According to Intel Controller Hub (ICH) specifications, the TCO watchdog has a 32 bytes I/O space resource. ACPI OperationRegions in the DSDT frequently reserve this TCO I/O space because they require access to bit 9 (DMISCI_STS) of the TCO1_STS register of the TCO, however, this bit is never used by the lpc_ich driver, so there is no risk of conflict. In the vast majority of cases this warning can be ignored as no harm will occur.",
> +   "label": "KlogAcpiSystemIOConflictLpcIchWatchDogTimer",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_LOW",
> +   "tag": "FWTS_TAG_ACPI",
> +   "pattern": "lpc_ich: Resource conflict(s) found affecting gpio_ich",
> +   "advice": "A resource conflict has occurred between ACPI OperationRegions and the same I/O region used by the lpc_ich driver for the General Purpose I/O (GPIO) region. Sometimes this GPIO region is used by the firmware for rfkill or LED controls or very rarely for the Embedded Controller System Control Interrupt. This may require deeper inspection to check if the conflict will lead to any real issues.  However, in the vast majority of cases this warning can be ignored as no harm will occur.",
> +   "label": "KlogAcpiSystemIOConflictLpcIchWatchDogTimer",
> +  },
> +  {
>      "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 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.",
> +   "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.  (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). 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": "KlogAcpiSystemIOConflict",
>     },
>     {
>
Acked-by: Alex Hung <alex.hung@canonical.com>
Ivan Hu - June 10, 2013, 6:53 a.m.
On 06/05/2013 09:23 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> These warnings are occuring frequently nowadays, and for most cases they
> are not a real issue at all. Add some more specific advice to put the warning
> into context.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>   data/klog.json | 18 +++++++++++++++++-
>   1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/data/klog.json b/data/klog.json
> index 9727894..2d297b2 100644
> --- a/data/klog.json
> +++ b/data/klog.json
> @@ -1362,11 +1362,27 @@
>      "label": "KlogACPIPrwEvalError"
>     },
>     {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_LOW",
> +   "tag": "FWTS_TAG_ACPI",
> +   "pattern": "lpc_ich: Resource conflict(s) found affecting iTCO_wdt",
> +   "advice": "A resource conflict has occurred between ACPI OperationRegions and the same I/O region used by the lpc_ich driver for the Intel TCO (Total Cost of Ownership) timer (iTCO_wdt, this is a watchdog timer that will reboot the machine after its second expiration). According to Intel Controller Hub (ICH) specifications, the TCO watchdog has a 32 bytes I/O space resource. ACPI OperationRegions in the DSDT frequently reserve this TCO I/O space because they require access to bit 9 (DMISCI_STS) of the TCO1_STS register of the TCO, however, this bit is never used by the lpc_ich driver, so there is no risk of conflict. In the vast majority of cases this warning can be ignored as no harm will occur.",
> +   "label": "KlogAcpiSystemIOConflictLpcIchWatchDogTimer",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_LOW",
> +   "tag": "FWTS_TAG_ACPI",
> +   "pattern": "lpc_ich: Resource conflict(s) found affecting gpio_ich",
> +   "advice": "A resource conflict has occurred between ACPI OperationRegions and the same I/O region used by the lpc_ich driver for the General Purpose I/O (GPIO) region. Sometimes this GPIO region is used by the firmware for rfkill or LED controls or very rarely for the Embedded Controller System Control Interrupt. This may require deeper inspection to check if the conflict will lead to any real issues.  However, in the vast majority of cases this warning can be ignored as no harm will occur.",
> +   "label": "KlogAcpiSystemIOConflictLpcIchWatchDogTimer",
> +  },
> +  {
>      "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 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.",
> +   "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.  (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). 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": "KlogAcpiSystemIOConflict",
>     },
>     {
>
Acked-by: Ivan Hu <ivan.hu@canonical.com>

Patch

diff --git a/data/klog.json b/data/klog.json
index 9727894..2d297b2 100644
--- a/data/klog.json
+++ b/data/klog.json
@@ -1362,11 +1362,27 @@ 
    "label": "KlogACPIPrwEvalError"
   },
   {
+   "compare_mode": "string",
+   "log_level": "LOG_LEVEL_LOW",
+   "tag": "FWTS_TAG_ACPI",
+   "pattern": "lpc_ich: Resource conflict(s) found affecting iTCO_wdt",
+   "advice": "A resource conflict has occurred between ACPI OperationRegions and the same I/O region used by the lpc_ich driver for the Intel TCO (Total Cost of Ownership) timer (iTCO_wdt, this is a watchdog timer that will reboot the machine after its second expiration). According to Intel Controller Hub (ICH) specifications, the TCO watchdog has a 32 bytes I/O space resource. ACPI OperationRegions in the DSDT frequently reserve this TCO I/O space because they require access to bit 9 (DMISCI_STS) of the TCO1_STS register of the TCO, however, this bit is never used by the lpc_ich driver, so there is no risk of conflict. In the vast majority of cases this warning can be ignored as no harm will occur.",
+   "label": "KlogAcpiSystemIOConflictLpcIchWatchDogTimer",
+  },
+  {
+   "compare_mode": "string",
+   "log_level": "LOG_LEVEL_LOW",
+   "tag": "FWTS_TAG_ACPI",
+   "pattern": "lpc_ich: Resource conflict(s) found affecting gpio_ich",
+   "advice": "A resource conflict has occurred between ACPI OperationRegions and the same I/O region used by the lpc_ich driver for the General Purpose I/O (GPIO) region. Sometimes this GPIO region is used by the firmware for rfkill or LED controls or very rarely for the Embedded Controller System Control Interrupt. This may require deeper inspection to check if the conflict will lead to any real issues.  However, in the vast majority of cases this warning can be ignored as no harm will occur.",
+   "label": "KlogAcpiSystemIOConflictLpcIchWatchDogTimer",
+  },
+  {
    "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 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.",
+   "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.  (Note that the lpc_ich driver can trigger these warnings, in which case they can generally be ignored). 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": "KlogAcpiSystemIOConflict",
   },
   {