Re: [lm-sensors] New Asus board and multiple sensors

[Marco Chiappero <marco@absence.it>]

[-- Attachment #1: Type: text/plain, Size: 3297 bytes --]

Rudolf Marek ha scritto:
> Hello,

Hi Rudolf, good to read you.

> DHG chip is wired as follows:
> 
> in0 is Vcore
> in1 is 12V
> in2 not used
> in3 is 3.3V
> in4 is 5V

Ok, maybe Stby +5V too?

> temp1 is MB temp
> fans are
> fan2 is cpu,
> fan5 is not, fan4 is not

Temp2 should be the CPU temp, fans1/fans4/fan5 should be cha1/cha2/cha3 
headers. I have created a file listing all the things I know and I'm 
able to manage with the w83627ehf driver. Take a look at:
http://www.absence.it/MIIF/sensors-output
http://www.absence.it/MIIF/w83667hg-report

> It measures:
> Cpu voltage, DDR voltage, SB 1.1V voltage SB 1.5V, CPU PLL voltage, NB 
> 1.1V Dram VTT volrage, VTT CPU voltage,

Right, these are the voltages show by the external LCD, so it makes 
sense to have these computed by another chip.

> So we need to find out what chip it is, because it measures a lot too.
> 
> The NB temperature etc etc is measured by some chip at 0x40 it seems it 
> also controls some fan temperature???

Don't know, since chassis1/2/3, CPU and Power Fan should be controlled 
by the w83667hg while the opt1/2/3 should be controlled by another chip, 
but can't say which one.

> Definitely what is the output of
> 
> i2cdetect 0
> i2cdump 0 0x40
> i2cdump 0 0x38

Output attached!
You may also read these and previous attachments by brousing 
http://www.absence.it/MIIF/

I have a question for you: are this probings harmless? Because I'm 
starting to experience a strange issue, and maybe you guys can help me 
to figure out why. But let me start from the beginning.
A few days ago, after many hours of uptime, the CPU temp (not the cores 
one) suddenly jumped to 110°C. Obviously it was a false positive, but it 
caused the sensors chip to push all my fans to the maximum speed and I 
had to reboot the computer to "solve" the problem. The day after exactly 
the same issue in the same way. Then reboot. The following day a really 
weird thing happened: suddenly many of the sensors of the board were no 
more available. Look at this screenshot I caught in that moment: 
http://www.absence.it/MIIF/errors.jpg
But this time after the OS closed all its stuff nor a reboot neither a 
reset made the computer boot again, so I had to press the power button. 
  A few hours later I have found a guy owning the same board and sharing 
almost the same issue that told me that this happens when running more 
than one sensors monitoring utility at time. It sounded strange to me 
but I was indeed running a couple of programs in those days (I've never 
used to do so before). Infact the day after the pc had no problems at 
all running just one monitoring tool as usual. However today, after 
using i2cdump for this attachment, I rebooted the computer to run these 
dumps on a newer kernel and that's the result: 
http://www.absence.it/MIIF/wrong-dumps
The same thing again! I rebooted but didn't work and I had to cut the 
power again. Have you got any idea about why this could happen? Is it an 
hardware (temporary?) fault or is it a software one? Or is it caused by 
any software? Above this the board has proven to be rock solid, so I 
don't know what to think: is the board defective? Is it normal?


Thank you again
Marco


[-- Attachment #2: MIIF-i2c-dumps --]
[-- Type: text/plain, Size: 3564 bytes --]

root@etna:/usr/src# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- 08 -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: 30 -- 32 33 -- 35 -- -- 38 -- -- -- -- -- -- -- 
40: 40 -- -- -- 44 -- -- -- -- -- -- -- -- -- -- -- 
50: 50 -- 52 -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
root@etna:/usr/src# i2cdump 0 0x38
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x38, mode byte
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: ff 55 a0 55 74 72 55 3f ff ff ff 01 00 ff ff ff    .U?UtrU?...?....
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
30: 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
80: ff ff ff ff ff ff ff ff ff ff 69 43 44 00 56 a1    ..........iCD.V?
90: 36 04 3e 08 64 04 dd 05 f8 05 5e 04 1c 04 5e 04    6?>?d?????^???^?
a0: e9 05 6f 03 ff 02 a5 02 ff ff ff ff 25 ff ff ff    ??o?.???....%...
b0: ff 08 00 07 23 00 00 00 20 ff ff ff ff ff ff ff    .?.?#... .......
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
root@etna:/usr/src# i2cdump 0 0x40
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x40, mode byte
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: ff ff ff ff ff ff ff 00 00 00 82 ff ff ff ff ff    ..........?.....
10: ff 50 50 ff 5a 5a 5a ff ff ff ff ff ff ff ff ff    .PP.ZZZ.........
20: ff ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff    ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
80: ff ff ff ff ff ff ff ff ff ff 50 cc 29 00 56 ec    ..........P?).V?
90: 00 00 df 05 00 00 d3 02 ff ff ff ff ff ff ff ff    ..??..??........
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: 24 2b 2c 23 20 1a 20 ff ff ff ff ff ff ff ff 00    $+,# ? .........
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................

[-- Attachment #3: Type: text/plain, Size: 153 bytes --]

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