From: Len Brown <lenb@kernel.org>
To: Chase Douglas <chase.douglas@ubuntu.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Reduce ACPI resource conflict message to KERN_INFO, printf cleanup
Date: Sun, 04 Apr 2010 21:13:03 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1004042107470.4155@localhost.localdomain> (raw)
In-Reply-To: <1269284889-3968-1-git-send-email-chase.douglas@ubuntu.com>
thanks,
Len Brown, Intel Open Source Technology Center
On Mon, 22 Mar 2010, Chase Douglas wrote:
> From: Chase Douglas <chase.douglas@canonical.com>
>
> By default, ACPI resource conflict messages are logged at level
> KERN_ERR. This is a rather high level for a message that is more a
> warning than an indication of a real kernel error. Also, KERN_ERR level
> messages can appear over some boot splash screens, and this message is
> not serious enough to warrant such treatment. Thus, the log level has
> been reduced to KERN_INFO.
>
> Also, cleanup message to use %pR resource printing format.
>
> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
> ---
> drivers/acpi/osl.c | 14 ++++----------
> 1 files changed, 4 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
> index 02e8464..33a01cb 100644
> --- a/drivers/acpi/osl.c
> +++ b/drivers/acpi/osl.c
> @@ -1151,16 +1151,10 @@ int acpi_check_resource_conflict(const struct resource *res)
>
> if (clash) {
> if (acpi_enforce_resources != ENFORCE_RESOURCES_NO) {
> - printk("%sACPI: %s resource %s [0x%llx-0x%llx]"
> - " conflicts with ACPI region %s"
> - " [0x%llx-0x%llx]\n",
> - acpi_enforce_resources == ENFORCE_RESOURCES_LAX
> - ? KERN_WARNING : KERN_ERR,
> - ioport ? "I/O" : "Memory", res->name,
> - (long long) res->start, (long long) res->end,
> - res_list_elem->name,
> - (long long) res_list_elem->start,
> - (long long) res_list_elem->end);
I think KERN_WARNING would be more appropriate here, as
this is a condition that may cause a devide driver to refuse to load...
I agree with skipping the check of acpi_enforce_resources here.
> + printk(KERN_INFO "ACPI: resource %s %pR"
> + " conflicts with ACPI region %s %pR\n",
> + res->name, res, res_list_elem->name,
> + res_list_elem);
> if (acpi_enforce_resources == ENFORCE_RESOURCES_LAX)
> printk(KERN_NOTICE "ACPI: This conflict may"
> " cause random problems and system"
> --
> 1.6.3.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-04-05 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 19:08 [PATCH] Reduce ACPI resource conflict message to KERN_INFO, printf cleanup Chase Douglas
2010-04-05 1:13 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-03 16:21 Chase Douglas
2010-03-17 14:15 ` Chase Douglas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.1004042107470.4155@localhost.localdomain \
--to=lenb@kernel.org \
--cc=chase.douglas@ubuntu.com \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox