From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Error message when ACPI causes a device probe to fail
Date: Fri, 02 Oct 2009 13:43:32 +0000 [thread overview]
Message-ID: <20091002154332.076fede2@hyperion.delvare> (raw)
Hi all,
We have recently added a mechanism to check for ACPI vs. native driver
resource conflicts. When such a conflict happens, we get an error
message of the following form in the logs:
ACPI: I/O resource 0000:00:1f.3 [0x18a0-0x18bf] conflicts with ACPI region SMBI [0x18a0-0x18af]
ACPI: Device needs an ACPI driver
But when the conflict is found in probe(), we also get the following
error message:
i801_smbus: probe of 0000:00:1f.3 failed with error -16
This is because the probe() method returns -EBUSY. The driver core
currently silents some error codes (ENODEV and ENXIO) but not EBUSY.
This error message is redundant with the ones printed by ACPI, and
somewhat more frightening, so users may report it to us, as was the
case here:
http://bugzilla.kernel.org/show_bug.cgi?id\x14293
So I would like to get rid of this message. I can think of two ways:
* Change the driver core to silent EBUSY as it does for ENODEV and
ENXIO. Greg, I guess you wouldn't like that?
* Change all drivers to return either -ENODEV or -ENXIO when an ACPI
resource conflict is found inside a probe function. After all, nobody
will ever see the error code in question so maybe it's acceptable
even though these error codes don't really match the reality?
Or maybe there's another fix possible and I did not see it. Feel free
to speak up if you have an idea.
Thanks,
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2009-10-02 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 13:43 Jean Delvare [this message]
2009-10-02 14:19 ` [lm-sensors] Error message when ACPI causes a device probe to Greg KH
2009-10-02 14:35 ` Jean Delvare
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=20091002154332.076fede2@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.