* [lm-sensors] sensors and i2cdump disagree on bus number
2007-01-23 5:14 [lm-sensors] sensors and i2cdump disagree on bus number Juerg Haefliger
@ 2007-01-23 8:35 ` Jean Delvare
2007-01-23 14:43 ` Juerg Haefliger
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2007-01-23 8:35 UTC (permalink / raw)
To: lm-sensors
Hi Juerg,
On Mon, 22 Jan 2007 21:14:57 -0800, Juerg Haefliger wrote:
> Hi all,
>
> When running sensors (2.10.1) I get the following adapter information:
> emc6d102-i2c-1-2e
> Adapter: SMBus nForce2 adapter at 4c40
>
> And i2cdump prints the following:
> Installed I2C busses:
> i2c-5 i2c NVIDIA i2c adapter 2 at 0:05.0
> i2c-4 i2c NVIDIA i2c adapter 1 at 0:05.0
> i2c-3 i2c NVIDIA i2c adapter 0 at 0:05.0
> i2c-2 i2c ivtv i2c driver #0
> i2c-1 smbus SMBus nForce2 adapter at 4c40
> i2c-0 smbus SMBus nForce2 adapter at 4c00
>
> But in order to dump the register content of the emc6d102 I have to scan bus
> 0:
>
> jabba:/home/juergh# i2cdump 0 0x2e
> 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 0x2e, mode byte
> Continue? [Y/n] y
> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 20: 00 79 c1 c2 be 80 29 31 46 0b ff ff ff ff ff ff .y????)1F?......
> 30: 55 ff ff 00 00 00 00 00 00 00 00 00 00 00 5c 8a U.............\?
> 40: 05 91 40 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f ??@...........??
> 50: 81 7f 81 7f ff ff ff ff ff ff ff ff 42 62 62 cb ????........Bbb?
> 60: cb db e0 00 55 80 80 5a 5a 3c 64 64 4d 40 40 00 ???.U??ZZ<ddM@@.
> 70: 55 ff ff 09 09 09 09 09 09 00 10 00 40 00 ec 18 U..??????.?. at .??
> 80: 7e a4 0e 00 60 90 99 90 c1 00 4d 4d 0b 0b 0d 00 ~??.`????.MM???.
> 90: 04 04 04 04 0c 0c 0c 5a f1 c2 00 00 ff 00 ff 00 ???????Z??......
> a0: 00 00 0c 00 02 00 00 0b 0b fe ff fe ff ff ff ff ..?.?..???.?....
> b0: ff 00 00 00 00 00 28 28 0e 0e 2b 2b 00 00 00 00 ......((??++....
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>
> Scanning bus 1 on the other hand returns all FFs:
>
> jabba:/home/juergh# i2cdump 1 0x2c
> 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-1, address 0x2c, mode byte
> Continue? [Y/n] y
> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
> 00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
Which kernel is this? 2.5 and early 2.6 kernels are known for this
behavior. It was fixed in 2.6.4. I guess you're using something more
recent though.
Is this bug reproducible, or did it only happen to you once?
When it happens, please run "ls -l /dev/i2c*" (or /dev/i2c/* if your
system uses this naming scheme.) I suspect that you have /dev/i2c-1
using minor 0 and /dev/i2c-0 using minor 1.
--
Jean Delvare
^ permalink raw reply [flat|nested] 6+ messages in thread* [lm-sensors] sensors and i2cdump disagree on bus number
2007-01-23 5:14 [lm-sensors] sensors and i2cdump disagree on bus number Juerg Haefliger
2007-01-23 8:35 ` Jean Delvare
@ 2007-01-23 14:43 ` Juerg Haefliger
2007-01-23 15:24 ` Jean Delvare
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Juerg Haefliger @ 2007-01-23 14:43 UTC (permalink / raw)
To: lm-sensors
Hi Jean
> Which kernel is this? 2.5 and early 2.6 kernels are known for this
> behavior. It was fixed in 2.6.4. I guess you're using something more
> recent though.
2.6.18.2
> Is this bug reproducible, or did it only happen to you once?
It's reproducible
> When it happens, please run "ls -l /dev/i2c*" (or /dev/i2c/* if your
> system uses this naming scheme.) I suspect that you have /dev/i2c-1
> using minor 0 and /dev/i2c-0 using minor 1.
Jan 23 06:39:26 localhost kernel: lm85 1-002e: Client (1,0x2e) config is
locked.
jabba:/home/juergh# sensors
emc6d102-i2c-1-2e
Adapter: SMBus nForce2 adapter at 4c40
in0: +3.33 V (min = +3.32 V, max = +3.32 V)
in1: +3.00 V (min = +2.99 V, max = +2.99 V)
in2: +4.40 V (min = +4.38 V, max = +4.38 V)
in3: +6.67 V (min = +6.64 V, max = +6.64 V)
in4: +16.00 V (min = +15.94 V, max = +15.94 V)
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: -0?C (low = -1?C, high = -1?C)
temp2: -0?C (low = -1?C, high = -1?C)
temp3: -0?C (low = -1?C, high = -1?C)
pwm1: 255
pwm2: 255
pwm3: 255
vid: +0.000 V (VRM Version 2.4)
jabba:/home/juergh# i2cdump 1 0x2e
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-1, address 0x2e, mode byte
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
jabba:/home/juergh# ls -l /dev/i2c-*
crw-rw---- 1 root root 89, 0 2007-01-23 06:37 /dev/i2c-0
crw-rw---- 1 root root 89, 1 2007-01-23 06:37 /dev/i2c-1
crw-rw---- 1 root root 89, 2 2007-01-23 06:37 /dev/i2c-2
crw-rw---- 1 root root 89, 3 2007-01-23 06:37 /dev/i2c-3
crw-rw---- 1 root root 89, 4 2007-01-23 06:37 /dev/i2c-4
crw-rw---- 1 root root 89, 5 2007-01-23 06:37 /dev/i2c-5
...juerg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070123/5531588c/attachment.html
^ permalink raw reply [flat|nested] 6+ messages in thread* [lm-sensors] sensors and i2cdump disagree on bus number
2007-01-23 5:14 [lm-sensors] sensors and i2cdump disagree on bus number Juerg Haefliger
2007-01-23 8:35 ` Jean Delvare
2007-01-23 14:43 ` Juerg Haefliger
@ 2007-01-23 15:24 ` Jean Delvare
2007-01-23 15:28 ` Juerg Haefliger
2007-01-23 15:32 ` Juerg Haefliger
4 siblings, 0 replies; 6+ messages in thread
From: Jean Delvare @ 2007-01-23 15:24 UTC (permalink / raw)
To: lm-sensors
Juerg,
On Tue, 23 Jan 2007 06:43:46 -0800, Juerg Haefliger wrote:
> > Which kernel is this? 2.5 and early 2.6 kernels are known for this
> > behavior. It was fixed in 2.6.4. I guess you're using something more
> > recent though.
>
> 2.6.18.2
>
> > Is this bug reproducible, or did it only happen to you once?
>
> It's reproducible
>
> > When it happens, please run "ls -l /dev/i2c*" (or /dev/i2c/* if your
> > system uses this naming scheme.) I suspect that you have /dev/i2c-1
> > using minor 0 and /dev/i2c-0 using minor 1.
>
> Jan 23 06:39:26 localhost kernel: lm85 1-002e: Client (1,0x2e) config is
> locked.
> jabba:/home/juergh# sensors
> emc6d102-i2c-1-2e
> Adapter: SMBus nForce2 adapter at 4c40
> in0: +3.33 V (min = +3.32 V, max = +3.32 V)
> in1: +3.00 V (min = +2.99 V, max = +2.99 V)
> in2: +4.40 V (min = +4.38 V, max = +4.38 V)
> in3: +6.67 V (min = +6.64 V, max = +6.64 V)
> in4: +16.00 V (min = +15.94 V, max = +15.94 V)
> fan1: 0 RPM (min = 0 RPM)
> fan2: 0 RPM (min = 0 RPM)
> fan3: 0 RPM (min = 0 RPM)
> fan4: 0 RPM (min = 0 RPM)
> temp1: -0?C (low = -1?C, high = -1?C)
> temp2: -0?C (low = -1?C, high = -1?C)
> temp3: -0?C (low = -1?C, high = -1?C)
> pwm1: 255
> pwm2: 255
> pwm3: 255
> vid: +0.000 V (VRM Version 2.4)
>
> jabba:/home/juergh# i2cdump 1 0x2e
> 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-1, address 0x2e, mode byte
> Continue? [Y/n] y
> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
> 00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> 90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
The dump actually matches the sensors output. Look at the sensors
values, they are all broken! I suspect you forced the driver to attach
to this specific bus and address, so it shows in "sensors", but there
really is no chip there. You probably just need to adjust your modprobe
options to force the driver to attach to the right bus.
> jabba:/home/juergh# ls -l /dev/i2c-*
> crw-rw---- 1 root root 89, 0 2007-01-23 06:37 /dev/i2c-0
> crw-rw---- 1 root root 89, 1 2007-01-23 06:37 /dev/i2c-1
> crw-rw---- 1 root root 89, 2 2007-01-23 06:37 /dev/i2c-2
> crw-rw---- 1 root root 89, 3 2007-01-23 06:37 /dev/i2c-3
> crw-rw---- 1 root root 89, 4 2007-01-23 06:37 /dev/i2c-4
> crw-rw---- 1 root root 89, 5 2007-01-23 06:37 /dev/i2c-5
This, on the other hand, looks just fine.
--
Jean Delvare
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lm-sensors] sensors and i2cdump disagree on bus number
2007-01-23 5:14 [lm-sensors] sensors and i2cdump disagree on bus number Juerg Haefliger
` (2 preceding siblings ...)
2007-01-23 15:24 ` Jean Delvare
@ 2007-01-23 15:28 ` Juerg Haefliger
2007-01-23 15:32 ` Juerg Haefliger
4 siblings, 0 replies; 6+ messages in thread
From: Juerg Haefliger @ 2007-01-23 15:28 UTC (permalink / raw)
To: lm-sensors
Hi Jean,
The problem seems to be somehow related to the forcing of the device. When I
modify the LM85 driver to autodetect my A8000 it works:
Jan 23 07:20:26 localhost kernel: i2c_adapter i2c-0: Detecting device at
0,0x2e with COMPANY: 0x5c and VERSTEP: 0x8a
Jan 23 07:20:26 localhost kernel: i2c_adapter i2c-0: Autodetecting device at
0,0x2e ...
Jan 23 07:20:26 localhost kernel: lm85 0-002e: Initializing device
Jan 23 07:20:27 localhost kernel: lm85 0-002e: LM85_REG_CONFIG is: 0x05
Jan 23 07:20:27 localhost kernel: lm85 0-002e: Setting CONFIG to: 0x05
jabba:~/hwmon# sensors
lm85b-i2c-0-2e
Adapter: SMBus nForce2 adapter at 4c00
V1.5: +0.00 V (min = +0.00 V, max = +3.32 V) ALARM
VCore: +1.42 V (min = +0.00 V, max = +2.99 V)
V3.3: +3.32 V (min = +0.00 V, max = +4.38 V)
V5: +5.05 V (min = +0.00 V, max = +6.64 V)
V12: +11.88 V (min = +0.00 V, max = +15.94 V)
CPU_Fan: 1860 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
CPU Temp: -128?C (low = -127?C, high = +127?C) ALARM FAULT
Board Temp:
+39?C (low = -127?C, high = +127?C)
Remote Temp:
+48?C (low = -127?C, high = +127?C)
CPU_PWM: 85
Fan2_PWM: 255
Fan3_PWM: 255
vid: +1.550 V (VRM Version 2.4)
...juerg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070123/17f383c9/attachment.html
^ permalink raw reply [flat|nested] 6+ messages in thread* [lm-sensors] sensors and i2cdump disagree on bus number
2007-01-23 5:14 [lm-sensors] sensors and i2cdump disagree on bus number Juerg Haefliger
` (3 preceding siblings ...)
2007-01-23 15:28 ` Juerg Haefliger
@ 2007-01-23 15:32 ` Juerg Haefliger
4 siblings, 0 replies; 6+ messages in thread
From: Juerg Haefliger @ 2007-01-23 15:32 UTC (permalink / raw)
To: lm-sensors
Jean,
> The dump actually matches the sensors output. Look at the sensors
> values, they are all broken! I suspect you forced the driver to attach
> to this specific bus and address, so it shows in "sensors", but there
> really is no chip there. You probably just need to adjust your modprobe
> options to force the driver to attach to the right bus.
Hmm... How would I do that? I did 'modprobe lm85 force_emc6d102=1,0x2e'
duh, I just realized that force_emc6d102=1 means bus 1 and not enable forcing...
Thanks, all's fine
...juerg
^ permalink raw reply [flat|nested] 6+ messages in thread