| Message ID | 1370335019-19398-1-git-send-email-colin.king@canonical.com |
|---|---|
| State | Accepted |
| Headers | show |
On Tue, Jun 4, 2013 at 4:36 PM, Colin King <colin.king@canonical.com> wrote: > From: Colin Ian King <colin.king@canonical.com> > > Fix spelling mistake "paramater" -> "parameter" > > Signed-off-by: Colin Ian King <colin.king@canonical.com> > --- > data/klog.json | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/data/klog.json b/data/klog.json > index cb55071..b581d1b 100644 > --- a/data/klog.json > +++ b/data/klog.json > @@ -1366,7 +1366,7 @@ > "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.", > + "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": "KlogAcpiSystemIOConflict", > }, > { > -- > 1.8.1.2 > Acked-by: Keng-Yu Lin <kengyu@canonical.com>
On 06/04/2013 04:36 PM, Colin King wrote: > From: Colin Ian King <colin.king@canonical.com> > > Fix spelling mistake "paramater" -> "parameter" > > Signed-off-by: Colin Ian King <colin.king@canonical.com> > --- > data/klog.json | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/data/klog.json b/data/klog.json > index cb55071..b581d1b 100644 > --- a/data/klog.json > +++ b/data/klog.json > @@ -1366,7 +1366,7 @@ > "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.", > + "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": "KlogAcpiSystemIOConflict", > }, > { > Acked-by: Alex Hung <alex.hung@canonical.com>
diff --git a/data/klog.json b/data/klog.json index cb55071..b581d1b 100644 --- a/data/klog.json +++ b/data/klog.json @@ -1366,7 +1366,7 @@ "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.", + "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": "KlogAcpiSystemIOConflict", }, {