From: Jean Delvare <jdelvare@suse.de>
To: linux-acpi@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
Len Brown <len.brown@intel.com>
Cc: Thomas Renninger <trenn@suse.de>,
Alan Jenkins <sourcejedi.lkml@googlemail.com>
Subject: Re: [PATCH v2] ACPI: Clarify resource conflict message
Date: Mon, 21 Sep 2009 10:25:40 +0200 [thread overview]
Message-ID: <200909211025.40605.jdelvare@suse.de> (raw)
In-Reply-To: <200909081531.46716.jdelvare@suse.de>
Len, Rui, can you please push this patch upstream quickly? We get
more and more reports about this, and an improved wording would
definitely help.
Thanks.
Le mardi 08 septembre 2009, Jean Delvare a écrit :
> From: Jean Delvare <jdelvare@suse.de>
> Subject: ACPI: Clarify resource conflict message
>
> The message "ACPI: Device needs an ACPI driver" is misleading. The
> device _may_ need an ACPI driver, if the BIOS implemented a custom
> API for the device in question (which, AFAIK, can't be checked.) If
> not, then either a generic ACPI driver may be used (for example
> "thermal"), or nothing can be done (other than a white list).
>
> I propose to reword the message to:
>
> ACPI: If an ACPI driver is available for this device, you should use
> it instead of the native driver
>
> which I think is more correct. Comments and suggestions welcome.
>
> I also added a message warning about possible problems and system
> instability when users pass acpi_enforce_resources=lax, as suggested
> by Len.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Cc: Zhang Rui <rui.zhang@intel.com>
> Cc: Len Brown <len.brown@intel.com>
> Cc: Thomas Renninger <trenn@suse.de>
> Cc: Alan Jenkins <sourcejedi.lkml@googlemail.com>
> ---
> Len, if you are satisfied with the wording, any chance to have this
> patch in 2.6.31? Thanks.
>
> drivers/acpi/osl.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> --- linux-2.6.31-rc9.orig/drivers/acpi/osl.c 2009-09-08 09:46:51.000000000 +0200
> +++ linux-2.6.31-rc9/drivers/acpi/osl.c 2009-09-08 13:56:53.000000000 +0200
> @@ -1182,7 +1182,13 @@ int acpi_check_resource_conflict(struct
> res_list_elem->name,
> (long long) res_list_elem->start,
> (long long) res_list_elem->end);
> - printk(KERN_INFO "ACPI: Device needs an ACPI driver\n");
> + if (acpi_enforce_resources == ENFORCE_RESOURCES_LAX)
> + printk(KERN_NOTICE "ACPI: This conflict may"
> + " cause random problems and system"
> + " instability\n");
> + printk(KERN_INFO "ACPI: If an ACPI driver is available"
> + " for this device, you should use it instead of"
> + " the native driver\n");
> }
> if (acpi_enforce_resources == ENFORCE_RESOURCES_STRICT)
> return -EBUSY;
>
--
Jean Delvare
Suse L3
--
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:[~2009-09-21 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 13:31 [PATCH v2] ACPI: Clarify resource conflict message Jean Delvare
2009-09-21 8:25 ` Jean Delvare [this message]
2009-09-27 7:12 ` Len Brown
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=200909211025.40605.jdelvare@suse.de \
--to=jdelvare@suse.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sourcejedi.lkml@googlemail.com \
--cc=trenn@suse.de \
/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