[lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Phillip Pi]

Hello.

This morning, I rebooted my old Debian box to start using its new Kernel
2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
(voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
using a MSI K8N NEO4-F (MS-7125) motherboard. You can see
http://alpha.zimage.com/~ant/antfarm/about/computers.txt for the
detailed hardware setup.

$ sensors -f
acpitz-virtual-0
Adapter: Virtual device
temp1:       +71.2�F  (crit = +206.2�F)

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:  +87.8�F
Core1 Temp:  +64.4�F


Kernel 2.6.30 and earlier used to say something like this:
$ sensors -f
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +80.6�F

...
Adapter: ISA adapter
VCore: +1.12 V (min = +2.11 V, max = +2.48 V)
+3.3V: +3.28 V (min = +1.46 V, max = +0.21 V)
+5V: +4.97 V (min = +0.89 V, max = +0.22 V)
+12V: +11.43 V (min = +0.24 V, max = +9.67 V)
-12V: +0.72 V (min = -5.37 V, max = +0.63 V)
-5V: +5.10 V (min = +1.18 V, max = -7.66 V)
V5SB: +5.59 V (min = +0.13 V, max = +0.48 V)
VBat: +1.55 V (min = +2.24 V, max = +3.46 V)
fan1: 2360 RPM (min = 1622 RPM, div = 4)
fan2: 2376 RPM (min = 1985 RPM, div = 4)
temp1: +82.4�F (high = +201.2°F, hyst = +221.0°F) sensor = thermistor
temp2: +86.0�F (high = +176.0°F, hyst = +167.0°F) sensor = thermistor
beep_enable:enabled 

I even reran sensors-detect command as shown in http://pastie.org/856408 
(too long to show in this post/e-mail).

I looked at the FAQ and saw 
http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31 
which look like my issue and matches dmesg: http://pastie.org/856424 ...

I am scared to use the lax method since it is not recommended. Is there 
another way to show the datas safely? Or do I have to use this trick or 
live without them?

Thank you in advance. :)
-- 
Quote of the Week: "Not all ants use violence to dominate their world,
some use more subtle methods..." --E.O. Wilson on NOVA
  /\___/\
 / /\ /\ \         Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |                Ant's Quality Foraged Links: http://aqfl.net
   \ _ /                 E-mail: philpi@earthlink.net or ant@zimage.com
    ( )

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Luca Tettamanti]

On Fri, Mar 5, 2010 at 11:20 PM, Phillip Pi <ant@zimage.com> wrote:
> This morning, I rebooted my old Debian box to start using its new Kernel
> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
> using a MSI K8N NEO4-F (MS-7125) motherboard.
[...]
> I looked at the FAQ and saw
> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
> which look like my issue and matches dmesg: http://pastie.org/856424 ...
>
> I am scared to use the lax method since it is not recommended. Is there
> another way to show the datas safely? Or do I have to use this trick or
> live without them?

Asus provides an ACPI interface for accessing the sensors in a safe
way; I don't know what it's used on MSI boards, but I can take a look:
please send me a dump of the DSDT table
(/sys/firmware/acpi/tables/DSDT).

Luca

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Luca Tettamanti]

On Sat, Mar 6, 2010 at 1:02 AM, Luca Tettamanti <kronos.it@gmail.com> wrote:
> On Fri, Mar 5, 2010 at 11:20 PM, Phillip Pi <ant@zimage.com> wrote:
>> This morning, I rebooted my old Debian box to start using its new Kernel
>> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
>> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
>> using a MSI K8N NEO4-F (MS-7125) motherboard.
> [...]
>> I looked at the FAQ and saw
>> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
>> which look like my issue and matches dmesg: http://pastie.org/856424 ...
>>
>> I am scared to use the lax method since it is not recommended. Is there
>> another way to show the datas safely? Or do I have to use this trick or
>> live without them?
>
> Asus provides an ACPI interface for accessing the sensors in a safe
> way; I don't know what it's used on MSI boards, but I can take a look:
> please send me a dump of the DSDT table

Nothing interesting in the DSDT; the hwmon chip is used only for
reading a temperature (TZ).
I think you can use "acpi_enforce_resources=lax", there not other ways
to access the sensor data.

Luca

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Phillip Pi]

> > >> This morning, I rebooted my old Debian box to start using its new Kernel
> > >> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
> > >> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
> > >> using a MSI K8N NEO4-F (MS-7125) motherboard.
> > > [...]
> > >> I looked at the FAQ and saw
> > >> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
> > >> which look like my issue and matches dmesg: http://pastie.org/856424 ...
> > >>
> > >> I am scared to use the lax method since it is not recommended. Is there
> > >> another way to show the datas safely? Or do I have to use this trick or
> > >> live without them?
> > >
> > > Asus provides an ACPI interface for accessing the sensors in a safe
> > > way; I don't know what it's used on MSI boards, but I can take a look:
> > > please send me a dump of the DSDT table
> > 
> > Nothing interesting in the DSDT; the hwmon chip is used only for
> > reading a temperature (TZ).
> > I think you can use "acpi_enforce_resources=lax", there not other ways
> > to access the sensor data.

Are there be any future plans to show voltages and other datas without 
the old method ("acpi_enforce_resources=lax")?
-- 
Quote of the Week: "This isn't a war. It never was a war, any more than
there's war between man and ants." --artilleryman from H.G. Wells' The
War of the Worlds
  /\___/\
 / /\ /\ \         Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |                Ant's Quality Foraged Links: http://aqfl.net
   \ _ /                 E-mail: philpi@earthlink.net or ant@zimage.com
    ( )

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Jean Delvare]

On Mon, 8 Mar 2010 21:57:25 +0100, Luca Tettamanti wrote:
> On Sat, Mar 6, 2010 at 1:02 AM, Luca Tettamanti <kronos.it@gmail.com> wrote:
> > On Fri, Mar 5, 2010 at 11:20 PM, Phillip Pi <ant@zimage.com> wrote:
> >> This morning, I rebooted my old Debian box to start using its new Kernel
> >> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
> >> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
> >> using a MSI K8N NEO4-F (MS-7125) motherboard.
> > [...]
> >> I looked at the FAQ and saw
> >> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
> >> which look like my issue and matches dmesg: http://pastie.org/856424 ...
> >>
> >> I am scared to use the lax method since it is not recommended. Is there
> >> another way to show the datas safely? Or do I have to use this trick or
> >> live without them?
> >
> > Asus provides an ACPI interface for accessing the sensors in a safe
> > way; I don't know what it's used on MSI boards, but I can take a look:
> > please send me a dump of the DSDT table
> 
> Nothing interesting in the DSDT; the hwmon chip is used only for
> reading a temperature (TZ).
> I think you can use "acpi_enforce_resources=lax", there not other ways
> to access the sensor data.

If you do, please make sure to blacklist the ACPI "thermal" driver.

-- 
Jean Delvare

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Luca Tettamanti]

(don't strip the CC list)

On Mon, Mar 8, 2010 at 10:10 PM, Phillip Pi <ant@zimage.com> wrote:
>> > >> This morning, I rebooted my old Debian box to start using its new Kernel
>> > >> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
>> > >> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
>> > >> using a MSI K8N NEO4-F (MS-7125) motherboard.
>> > > [...]
>> > >> I looked at the FAQ and saw
>> > >> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
>> > >> which look like my issue and matches dmesg: http://pastie.org/856424 ...
>> > >>
>> > >> I am scared to use the lax method since it is not recommended. Is there
>> > >> another way to show the datas safely? Or do I have to use this trick or
>> > >> live without them?
>> > >
>> > > Asus provides an ACPI interface for accessing the sensors in a safe
>> > > way; I don't know what it's used on MSI boards, but I can take a look:
>> > > please send me a dump of the DSDT table
>> >
>> > Nothing interesting in the DSDT; the hwmon chip is used only for
>> > reading a temperature (TZ).
>> > I think you can use "acpi_enforce_resources=lax", there not other ways
>> > to access the sensor data.
>
> Thanks Luca. I assume it is safe to use for my motherboard to see other
> datas like voltages?

Not 100%, there's still a race window. But it's pretty small.

> Are there be any future plans to show voltages and other datas without
> the old method ("acpi_enforce_resources=lax")?

We can't do much... the IO ports used by the monitoring chip are
claimed by ACPI (supplied by the board vendor), so technically it's
wrong for another driver to poke it. Asus provides an interface for
reading the sensors in safe way, MSI does not...

Luca

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Phillip Pi]

> > >> This morning, I rebooted my old Debian box to start using its new Kernel
> > >> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
> > >> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
> > >> using a MSI K8N NEO4-F (MS-7125) motherboard.
> > > [...]
> > >> I looked at the FAQ and saw
> > >> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
> > >> which look like my issue and matches dmesg: http://pastie.org/856424 ...
> > >>
> > >> I am scared to use the lax method since it is not recommended. Is there
> > >> another way to show the datas safely? Or do I have to use this trick or
> > >> live without them?
> > >
> > > Asus provides an ACPI interface for accessing the sensors in a safe
> > > way; I don't know what it's used on MSI boards, but I can take a look:
> > > please send me a dump of the DSDT table
> > 
> > Nothing interesting in the DSDT; the hwmon chip is used only for
> > reading a temperature (TZ).
> > I think you can use "acpi_enforce_resources=lax", there not other ways
> > to access the sensor data.
> 
> If you do, please make sure to blacklist the ACPI "thermal" driver.

Where do I set blacklist it? What is bad about "thermal" driver? 
Conflict?
-- 
Quote of the Week: "This isn't a war. It never was a war, any more than
there's war between man and ants." --artilleryman from H.G. Wells' The
War of the Worlds
  /\___/\
 / /\ /\ \         Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |                Ant's Quality Foraged Links: http://aqfl.net
   \ _ /                 E-mail: philpi@earthlink.net or ant@zimage.com
    ( )

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Phillip Pi]

> On Mon, Mar 8, 2010 at 10:10 PM, Phillip Pi <ant@zimage.com> wrote:
> >> > >> This morning, I rebooted my old Debian box to start using its new Kernel
> >> > >> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
> >> > >> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
> >> > >> using a MSI K8N NEO4-F (MS-7125) motherboard.
> >> > > [...]
> >> > >> I looked at the FAQ and saw
> >> > >> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
> >> > >> which look like my issue and matches dmesg: http://pastie.org/856424 ...
> >> > >>
> >> > >> I am scared to use the lax method since it is not recommended. Is there
> >> > >> another way to show the datas safely? Or do I have to use this trick or
> >> > >> live without them?
> >> > >
> >> > > Asus provides an ACPI interface for accessing the sensors in a safe
> >> > > way; I don't know what it's used on MSI boards, but I can take a look:
> >> > > please send me a dump of the DSDT table
> >> >
> >> > Nothing interesting in the DSDT; the hwmon chip is used only for
> >> > reading a temperature (TZ).
> >> > I think you can use "acpi_enforce_resources=lax", there not other ways
> >> > to access the sensor data.
> >
> > Thanks Luca. I assume it is safe to use for my motherboard to see other
> > datas like voltages?
> 
> Not 100%, there's still a race window. But it's pretty small.

What do you mean by race window? I am not familiar with this 
term/phrase.

 
> > Are there be any future plans to show voltages and other datas without
> > the old method ("acpi_enforce_resources=lax")?
> 
> We can't do much... the IO ports used by the monitoring chip are
> claimed by ACPI (supplied by the board vendor), so technically it's
> wrong for another driver to poke it. Asus provides an interface for
> reading the sensors in safe way, MSI does not...

So no one was able to hack MSI hardwares even after a few years? And MSI 
never released their datas? Is that why?
-- 
Quote of the Week: "This isn't a war. It never was a war, any more than
there's war between man and ants." --artilleryman from H.G. Wells' The
War of the Worlds
  /\___/\
 / /\ /\ \         Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |                Ant's Quality Foraged Links: http://aqfl.net
   \ _ /                 E-mail: philpi@earthlink.net or ant@zimage.com
    ( )

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Luca Tettamanti]

On Mon, Mar 8, 2010 at 10:17 PM, Jean Delvare <khali@linux-fr.org> wrote:
> On Mon, 8 Mar 2010 21:57:25 +0100, Luca Tettamanti wrote:
>> On Sat, Mar 6, 2010 at 1:02 AM, Luca Tettamanti <kronos.it@gmail.com> wrote:
>> >> I am scared to use the lax method since it is not recommended. Is there
>> >> another way to show the datas safely? Or do I have to use this trick or
>> >> live without them?
>> >
>> > Asus provides an ACPI interface for accessing the sensors in a safe
>> > way; I don't know what it's used on MSI boards, but I can take a look:
>> > please send me a dump of the DSDT table
>>
>> Nothing interesting in the DSDT; the hwmon chip is used only for
>> reading a temperature (TZ).
>> I think you can use "acpi_enforce_resources=lax", there not other ways
>> to access the sensor data.
>
> If you do, please make sure to blacklist the ACPI "thermal" driver.

Hum, I'd rather live with the race condition. The thermal driver is
also responsible for controlling the cooling state.
Would it be totally horrible to use acpi_ex_{enter,exit}_interpreter
inside hwmon code to serialize execution?

L

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Jean Delvare]

On Mon, 8 Mar 2010 13:28:55 -0800, Phillip Pi wrote:
> > > Nothing interesting in the DSDT; the hwmon chip is used only for
> > > reading a temperature (TZ).
> > > I think you can use "acpi_enforce_resources=lax", there not other ways
> > > to access the sensor data.
> > 
> > If you do, please make sure to blacklist the ACPI "thermal" driver.
>
> Where do I set blacklist it?

Depends on the distribution. Sometimes it's enough to add:

blacklist thermal

to /etc/modprobe.d/*.conf, but sometimes init scripts actively load the
thermal driver, so you have to hack them or at least edit
distro-specific config files.

> What is bad about "thermal" driver? 
> Conflict?

Yes. The thermal driver will access the same I/O ports as the w83627ehf
driver, without any synchronization between them, so very bad things
can happen.

-- 
Jean Delvare

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Phillip Pi]

> >> >> I am scared to use the lax method since it is not recommended. Is there
> >> >> another way to show the datas safely? Or do I have to use this trick or
> >> >> live without them?
> >> >
> >> > Asus provides an ACPI interface for accessing the sensors in a safe
> >> > way; I don't know what it's used on MSI boards, but I can take a look:
> >> > please send me a dump of the DSDT table
> >>
> >> Nothing interesting in the DSDT; the hwmon chip is used only for
> >> reading a temperature (TZ).
> >> I think you can use "acpi_enforce_resources=lax", there not other ways
> >> to access the sensor data.
> >
> > If you do, please make sure to blacklist the ACPI "thermal" driver.
> 
> Hum, I'd rather live with the race condition. The thermal driver is
> also responsible for controlling the cooling state.
> Would it be totally horrible to use acpi_ex_{enter,exit}_interpreter
> inside hwmon code to serialize execution?

Another thing. Is this going to be harmful if I enable AMD's
Cool'n'Quiet in its CMOS and use PowerNow-k8 module? I used to use it in 
the past, but currently disabled for testingn purposes.

modprobe powernow-k8
echo ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1 >/sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load
-- 
Quote of the Week: "This isn't a war. It never was a war, any more than
there's war between man and ants." --artilleryman from H.G. Wells' The
War of the Worlds
  /\___/\
 / /\ /\ \         Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |                Ant's Quality Foraged Links: http://aqfl.net
   \ _ /                 E-mail: philpi@earthlink.net or ant@zimage.com
    ( )

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Phillip Pi]

> > > > Nothing interesting in the DSDT; the hwmon chip is used only for
> > > > reading a temperature (TZ).
> > > > I think you can use "acpi_enforce_resources=lax", there not other ways
> > > > to access the sensor data.
> > > 
> > > If you do, please make sure to blacklist the ACPI "thermal" driver.
> >
> > Where do I set blacklist it?
> 
> Depends on the distribution. Sometimes it's enough to add:
> 
> blacklist thermal
> 
> to /etc/modprobe.d/*.conf, but sometimes init scripts actively load the
> thermal driver, so you have to hack them or at least edit
> distro-specific config files.

Thanks. I see existing files in mine:
$ ls /etc/modprobe.d/
aliases.conf              blacklist-bluetooth   libpisock9.conf
alsa-base-blacklist.conf  blacklist.conf        linux-sound-base_noOSS.conf
alsa-base.conf            fbdev-blacklist.conf  oss-compat.conf


> > What is bad about "thermal" driver? 
> > Conflict?
> 
> Yes. The thermal driver will access the same I/O ports as the w83627ehf
> driver, without any synchronization between them, so very bad things
> can happen.

In older Kernels like v2.6.30, did this conflict happen too? I only 
remember seeing inaccurate values like for voltages. Speaking of 
voltages, which part is responsibile for voltages showing that I don't 
have in 2.6.32, but did in 2.6.30?
-- 
Quote of the Week: "This isn't a war. It never was a war, any more than
there's war between man and ants." --artilleryman from H.G. Wells' The
War of the Worlds
  /\___/\
 / /\ /\ \         Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |                Ant's Quality Foraged Links: http://aqfl.net
   \ _ /                 E-mail: philpi@earthlink.net or ant@zimage.com
    ( )

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Luca Tettamanti]

On Mon, Mar 8, 2010 at 10:31 PM, Phillip Pi <ant@zimage.com> wrote:
>> On Mon, Mar 8, 2010 at 10:10 PM, Phillip Pi <ant@zimage.com> wrote:
>> >> > >> This morning, I rebooted my old Debian box to start using its new Kernel
>> >> > >> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
>> >> > >> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
>> >> > >> using a MSI K8N NEO4-F (MS-7125) motherboard.
>> >> > > [...]
>> >> > >> I looked at the FAQ and saw
>> >> > >> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
>> >> > >> which look like my issue and matches dmesg: http://pastie.org/856424 ...
>> >> > >>
>> >> > >> I am scared to use the lax method since it is not recommended. Is there
>> >> > >> another way to show the datas safely? Or do I have to use this trick or
>> >> > >> live without them?
>> >> > >
>> >> > > Asus provides an ACPI interface for accessing the sensors in a safe
>> >> > > way; I don't know what it's used on MSI boards, but I can take a look:
>> >> > > please send me a dump of the DSDT table
>> >> >
>> >> > Nothing interesting in the DSDT; the hwmon chip is used only for
>> >> > reading a temperature (TZ).
>> >> > I think you can use "acpi_enforce_resources=lax", there not other ways
>> >> > to access the sensor data.
>> >
>> > Thanks Luca. I assume it is safe to use for my motherboard to see other
>> > datas like voltages?
>>
>> Not 100%, there's still a race window. But it's pretty small.
>
> What do you mean by race window? I am not familiar with this
> term/phrase.

There a small temporal window when the two drivers (thermal and native
driver) might access the chip at the same time leading to incorrect
readings (or worse).

>> > Are there be any future plans to show voltages and other datas without
>> > the old method ("acpi_enforce_resources=lax")?
>>
>> We can't do much... the IO ports used by the monitoring chip are
>> claimed by ACPI (supplied by the board vendor), so technically it's
>> wrong for another driver to poke it. Asus provides an interface for
>> reading the sensors in safe way, MSI does not...
>
> So no one was able to hack MSI hardwares even after a few years? And MSI
> never released their datas? Is that why?

No, ACPI code is basically embedded in the BIOS, so there's no way to
expand the interface - short of providing a custom BIOS for each
board.
The problem is that two pieces of software are trying to control the
same hw resource without any coordination.

Luca

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Jean Delvare]

On Mon, 8 Mar 2010 13:39:19 -0800, Phillip Pi wrote:
> Another thing. Is this going to be harmful if I enable AMD's
> Cool'n'Quiet in its CMOS and use PowerNow-k8 module? I used to use it in 
> the past, but currently disabled for testingn purposes.

No, the powernow-k8 driver doesn't use the problematic I/O ports so it
won't cause any problem.

> modprobe powernow-k8
> echo ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> echo 1 >/sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load


-- 
Jean Delvare

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Jean Delvare]

Hi Luca,

On Mon, 8 Mar 2010 22:34:49 +0100, Luca Tettamanti wrote:
> Would it be totally horrible to use acpi_ex_{enter,exit}_interpreter
> inside hwmon code to serialize execution?

I would be totally in favor of it if it solves actual problems (or any
functionally equivalent solution). I guess it can't be bullet-proof, as
both the native driver and ACPI can assume state conservation between
device accesses, which is no longer guaranteed with someone else
accessing the device, but it should indeed help solve at least the most
critical problems.

Can you please prepare a patch and send it to both the ACPI folks and
the lm-sensors list?

-- 
Jean Delvare

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Jean Delvare]

Hi Phillip,

On Mon, 8 Mar 2010 13:43:14 -0800, Phillip Pi wrote:
> In older Kernels like v2.6.30, did this conflict happen too? I only 
> remember seeing inaccurate values like for voltages. Speaking of 
> voltages, which part is responsibile for voltages showing that I don't 
> have in 2.6.32, but did in 2.6.30?

Please be specific. What chip is it, which voltages are missing?

Remember that the output of sensors is influenced by the contents of
libsensors configuration files (/etc/sensors.conf, /etc/sensors3.conf
and/or /etc/sensors.d/* depending on your libsensors version and
distribution choices.)

-- 
Jean Delvare

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Phillip Pi]

> On Mon, 8 Mar 2010 13:43:14 -0800, Phillip Pi wrote:
> > In older Kernels like v2.6.30, did this conflict happen too? I only 
> > remember seeing inaccurate values like for voltages. Speaking of 
> > voltages, which part is responsibile for voltages showing that I don't 
> > have in 2.6.32, but did in 2.6.30?
> 
> Please be specific. What chip is it, which voltages are missing?

AMD Athlon X2 939 CPU 4600+ and MSI K8N NEO4-F (MS-7125) motherboard
(NVIDIA nForce4). See my secondary computer details at:
http://alpha.zimage.com/~ant/antfarm/about/computers.txt

As for voltages, Kernel 2.6.30 and earlier said something like:
$ sensors -f
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +80.6�F
...
Adapter: ISA adapter
VCore: +1.12 V (min = +2.11 V, max = +2.48 V)
+3.3V: +3.28 V (min = +1.46 V, max = +0.21 V)
+5V: +4.97 V (min = +0.89 V, max = +0.22 V)
+12V: +11.43 V (min = +0.24 V, max = +9.67 V)
-12V: +0.72 V (min = -5.37 V, max = +0.63 V)
-5V: +5.10 V (min = +1.18 V, max = -7.66 V)
V5SB: +5.59 V (min = +0.13 V, max = +0.48 V)
VBat: +1.55 V (min = +2.24 V, max = +3.46 V)
fan1: 2360 RPM (min = 1622 RPM, div = 4)
fan2: 2376 RPM (min = 1985 RPM, div = 4)
temp1: +82.4�F (high = +201.2°F, hyst = +221.0°F) sensor = 
thermistor
temp2: +86.0�F (high = +176.0°F, hyst = +167.0°F) sensor = 
thermistor
beep_enable:enabled

I even reran sensors-detect command as shown in http://pastie.org/856408
(too long to show in this post/e-mail).

 
> Remember that the output of sensors is influenced by the contents of
> libsensors configuration files (/etc/sensors.conf, /etc/sensors3.conf
> and/or /etc/sensors.d/* depending on your libsensors version and
> distribution choices.)

I always keep my lm_sensors packages updated so whatever they gave me is 
what I use. The only I edited was /etc/modules based on sensors-detect 
results (w83627ehf). I do not recall editing sensors*.conf files or 
being asked to do so.
-- 
Quote of the Week: "This isn't a war. It never was a war, any more than
there's war between man and ants." --artilleryman from H.G. Wells' The
War of the Worlds
  /\___/\
 / /\ /\ \         Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |                Ant's Quality Foraged Links: http://aqfl.net
   \ _ /                 E-mail: philpi@earthlink.net or ant@zimage.com
    ( )

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Jean Delvare]

On Tue, 9 Mar 2010 01:05:58 -0800, Phillip Pi wrote:
> > Please be specific. What chip is it, which voltages are missing?
> 
> AMD Athlon X2 939 CPU 4600+ and MSI K8N NEO4-F (MS-7125) motherboard
> (NVIDIA nForce4). See my secondary computer details at:
> http://alpha.zimage.com/~ant/antfarm/about/computers.txt
> 
> As for voltages, Kernel 2.6.30 and earlier said something like:
> $ sensors -f
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp: +80.6°F
> ...

Please stop editing outputs. You are stripping exactly the information
I asked for (what chip it is.)

> Adapter: ISA adapter
> VCore: +1.12 V (min = +2.11 V, max = +2.48 V)
> +3.3V: +3.28 V (min = +1.46 V, max = +0.21 V)
> +5V: +4.97 V (min = +0.89 V, max = +0.22 V)
> +12V: +11.43 V (min = +0.24 V, max = +9.67 V)
> -12V: +0.72 V (min = -5.37 V, max = +0.63 V)
> -5V: +5.10 V (min = +1.18 V, max = -7.66 V)
> V5SB: +5.59 V (min = +0.13 V, max = +0.48 V)
> VBat: +1.55 V (min = +2.24 V, max = +3.46 V)
> fan1: 2360 RPM (min = 1622 RPM, div = 4)
> fan2: 2376 RPM (min = 1985 RPM, div = 4)
> temp1: +82.4°F (high = +201.2°F, hyst = +221.0°F) sensor = 
> thermistor
> temp2: +86.0°F (high = +176.0°F, hyst = +167.0°F) sensor = 
> thermistor
> beep_enable:enabled

OK, and how do I compare this with 2.6.32 if you do not provide the
output there?

> > Remember that the output of sensors is influenced by the contents of
> > libsensors configuration files (/etc/sensors.conf, /etc/sensors3.conf
> > and/or /etc/sensors.d/* depending on your libsensors version and
> > distribution choices.)
> 
> I always keep my lm_sensors packages updated so whatever they gave me is 
> what I use. The only I edited was /etc/modules based on sensors-detect 
> results (w83627ehf). I do not recall editing sensors*.conf files or 
> being asked to do so.

This doesn't mean they haven't changed. We ship a default configuration
file, which does change over time. That being said, it does _not_
contain arbitrary ignore statements, so should not be responsible for
inputs mysteriously disappearing.

-- 
Jean Delvare

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Phillip Pi]

> > > Please be specific. What chip is it, which voltages are missing?
> > 
> > AMD Athlon X2 939 CPU 4600+ and MSI K8N NEO4-F (MS-7125) motherboard
> > (NVIDIA nForce4). See my secondary computer details at:
> > http://alpha.zimage.com/~ant/antfarm/about/computers.txt
> > 
> > As for voltages, Kernel 2.6.30 and earlier said something like:
> > $ sensors -f
> > k8temp-pci-00c3
> > Adapter: PCI adapter
> > Core0 Temp: +80.6°F
> > ...
> 
> Please stop editing outputs. You are stripping exactly the information
> I asked for (what chip it is.)
 
> > Adapter: ISA adapter
> > VCore: +1.12 V (min = +2.11 V, max = +2.48 V)
> > +3.3V: +3.28 V (min = +1.46 V, max = +0.21 V)
> > +5V: +4.97 V (min = +0.89 V, max = +0.22 V)
> > +12V: +11.43 V (min = +0.24 V, max = +9.67 V)
> > -12V: +0.72 V (min = -5.37 V, max = +0.63 V)
> > -5V: +5.10 V (min = +1.18 V, max = -7.66 V)
> > V5SB: +5.59 V (min = +0.13 V, max = +0.48 V)
> > VBat: +1.55 V (min = +2.24 V, max = +3.46 V)
> > fan1: 2360 RPM (min = 1622 RPM, div = 4)
> > fan2: 2376 RPM (min = 1985 RPM, div = 4)
> > temp1: +82.4°F (high = +201.2°F, hyst = +221.0°F) sensor = 
> > thermistor
> > temp2: +86.0°F (high = +176.0°F, hyst = +167.0°F) sensor = 
> > thermistor
> > beep_enable:enabled
> 
> OK, and how do I compare this with 2.6.32 if you do not provide the
> output there?

Huh? That's all I get. Here's the 2.6.32 one:

$ sensors -f
acpitz-virtual-0
Adapter: Virtual device
temp1:       +71.2°F  (crit = +206.2°F)                  

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:  +91.4°F                                    
Core1 Temp:  +69.8°F

Where is the chip parts?

 
> > > Remember that the output of sensors is influenced by the contents of
> > > libsensors configuration files (/etc/sensors.conf, /etc/sensors3.conf
> > > and/or /etc/sensors.d/* depending on your libsensors version and
> > > distribution choices.)
> > 
> > I always keep my lm_sensors packages updated so whatever they gave me is 
> > what I use. The only I edited was /etc/modules based on sensors-detect 
> > results (w83627ehf). I do not recall editing sensors*.conf files or 
> > being asked to do so.
> 
> This doesn't mean they haven't changed. We ship a default configuration
> file, which does change over time. That being said, it does _not_
> contain arbitrary ignore statements, so should not be responsible for
> inputs mysteriously disappearing.

Hmm.
-- 
Quote of the Week: "This isn't a war. It never was a war, any more than
there's war between man and ants." --artilleryman from H.G. Wells' The
War of the Worlds
  /\___/\
 / /\ /\ \         Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o   o| |                Ant's Quality Foraged Links: http://aqfl.net
   \ _ /                 E-mail: philpi@earthlink.net or ant@zimage.com
    ( )

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

Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to

[Jean Delvare]

On Tue, 9 Mar 2010 06:20:55 -0800, Phillip Pi wrote:
> > > > Please be specific. What chip is it, which voltages are missing?
> > > 
> > > AMD Athlon X2 939 CPU 4600+ and MSI K8N NEO4-F (MS-7125) motherboard
> > > (NVIDIA nForce4). See my secondary computer details at:
> > > http://alpha.zimage.com/~ant/antfarm/about/computers.txt
> > > 
> > > As for voltages, Kernel 2.6.30 and earlier said something like:
> > > $ sensors -f
> > > k8temp-pci-00c3
> > > Adapter: PCI adapter
> > > Core0 Temp: +80.6°F
> > > ...
> > 
> > Please stop editing outputs. You are stripping exactly the information
> > I asked for (what chip it is.)
>  
> > > Adapter: ISA adapter
> > > VCore: +1.12 V (min = +2.11 V, max = +2.48 V)
> > > +3.3V: +3.28 V (min = +1.46 V, max = +0.21 V)
> > > +5V: +4.97 V (min = +0.89 V, max = +0.22 V)
> > > +12V: +11.43 V (min = +0.24 V, max = +9.67 V)
> > > -12V: +0.72 V (min = -5.37 V, max = +0.63 V)
> > > -5V: +5.10 V (min = +1.18 V, max = -7.66 V)
> > > V5SB: +5.59 V (min = +0.13 V, max = +0.48 V)
> > > VBat: +1.55 V (min = +2.24 V, max = +3.46 V)
> > > fan1: 2360 RPM (min = 1622 RPM, div = 4)
> > > fan2: 2376 RPM (min = 1985 RPM, div = 4)
> > > temp1: +82.4°F (high = +201.2°F, hyst = +221.0°F) sensor = 
> > > thermistor
> > > temp2: +86.0°F (high = +176.0°F, hyst = +167.0°F) sensor = 
> > > thermistor
> > > beep_enable:enabled
> > 
> > OK, and how do I compare this with 2.6.32 if you do not provide the
> > output there?
> 
> Huh? That's all I get. Here's the 2.6.32 one:
> 
> $ sensors -f
> acpitz-virtual-0
> Adapter: Virtual device
> temp1:       +71.2°F  (crit = +206.2°F)                  
> 
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp:  +91.4°F                                    
> Core1 Temp:  +69.8°F
> 
> Where is the chip parts?

I'm confused. Luca has explained you all the details to get the
readings back if so were your desire. I thought you did that and had
further issues, but apparently no, you didn't do anything and keep
asking questions. The ball is in your court now, there's nothing more
we can do to help you.

-- 
Jean Delvare

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