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@xxxxxxxxx> 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@xxxxxxxxxxxxxx > http://lists.lm-sensors.org/mailman/listinfo/lm-sensors _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
