On Tue, 3 Nov 2009, Hauke Fath wrote:
At 9:43 Uhr -0800 03.11.2009, Paul Goyette wrote:
Just curious, can you try 'mbmon -S' to see if that's how it is
getting its data?
Looks very similar, apart from Temp1:
# mbmon -S
Temp.= 33.0, 33.0, 0.0; Rot.= 3341, 0, 0
Vcore = 2.06, 2.51; Volt. = 3.65, 5.05, 11.80, -11.29, -5.14
^C
# envstat
Current CritMax CritMin CritCap Unit
[lm0]
VCore A: 2.064 V
VCore B: 2.512 V
+3.3V: 3.648 V
+5V: 5.053 V
+12V: 11.795 V
-12V: -11.126 V
-5V: -5.153 V
Temp0: 33.000 degC
Temp1: 0.000 degC
Temp2: 0.000 degC
Fan0: 3341 RPM
Fan1: N/A
Fan2: N/A
#
Yeah, than confirms that mbmon is using SMBus access.
I'm suspecting that there's some contention between the piixpm i2c
driver and ACPI's SMBus accessing the same bus. This can cause all
sorts of issues.
I've written a ACPI SMBus i2c driver to use ACPI access directly,
but it requires manually disabling the "native" i2c drivers since
there's no clean way to prevent simultaneous access. Perhaps you
might want to try my driver to see if you get more consistent and
reliable results? (See attachment.)
I'll give that a try tomorrow.
Great! Make sure you remove 'iic* at piixpm?' from your config.