All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Using dme1737 to read sensor data when an ACPI
Date: Mon, 21 Feb 2011 23:04:44 +0000	[thread overview]
Message-ID: <20110221230444.GA10800@ericsson.com> (raw)
In-Reply-To: <AANLkTikYuVDyhet3uT7u1Vivw908C31wsqfp=wg0qgkd@mail.gmail.com>

On Mon, Feb 21, 2011 at 01:30:31PM -0500, James Mills wrote:
> Does anyone have any information on my question below?  I would just
> like to put my mind at ease if at all possible.  Again, I will only be
> using this module to poll sensors.
> 
Top-posting is discouraged.

Searching for dme1737, SCH3114 and acpi on the web suggests that there can be
interference between dme1737 and acpi, and that it is not a good idea to have
both active. There were a number of discussions about this issue on this forum, 
all suggesting the same.

Not sure what else can be said.

Guenter

> Thanks!
> ~james
> 
> On Wed, Feb 16, 2011 at 9:31 AM, James Mills <jameswmills@gmail.com> wrote:
> > All,
> >
> > I am working on a project with a SCH3114.  By default, when I modprobe
> > dme1737, it fails with an ACPI conflict.  In the short term, I have
> > added "acpi_enforce_resources=lax", and the module now loads and
> > sensors are displayed.
> >
> > However, I am concerned with the dmesg:
> >
> > ACPI: resource dme1737 [io  0x0a70-0x0a71] conflicts with ACPI region
> > RNTR [??? 0x00000a00-0x00000a7f flags 0x52]
> > ACPI: This conflict may cause random problems and system instability
> >
> > All we want is for the sensor data provided by this module to be
> > polled periodically.
> >
> > Can anyone tell me what the real risk is of using this module in
> > conjunction with "lax" ACPI?  Is there a way to put this module in
> > "read-only" mode or some other mode that minimizes the potential for
> > system instability?
> >
> > Any information is appreciated!
> > ~james
> >
> 
> 
> 
> -- 
> you've gotta live light enough to see the humor
> and long enough to see some change
> ~ Ani DiFranco
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2011-02-21 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 15:31 [lm-sensors] Using dme1737 to read sensor data when an ACPI James Mills
2011-02-21 18:30 ` James Mills
2011-02-21 23:04 ` Guenter Roeck [this message]
2011-02-22  7:50 ` [lm-sensors] Using dme1737 to read sensor data when an Clemens Ladisch
2011-02-22 16:08 ` [lm-sensors] Using dme1737 to read sensor data when an ACPI James Mills

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=20110221230444.GA10800@ericsson.com \
    --to=guenter.roeck@ericsson.com \
    --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.