[lm-sensors] LM85 problems with 2.6.16.x - 2.6.19.1

[lm-sensors] LM85 problems with 2.6.16.x - 2.6.19.1

[Holger Kiehl]

Hello

I am using a Tyan S4882 motherboard with 4 CPU's that has a LM85 sensor chip
which reports the following message during boot:

     .
     .
     ipmi device interface
     Enabling SMBus multiplexing for Tyan S4882
     lm85 0-002e: Client (0,0x2e) config is locked.
     lm85 0-002e: Client (0,0x2e) is not ready.
     lm85 0-002e: Client (0,0x2e) VxI mode is set. Please report this to the lm85 maintainer.

Looking at /var/log/messages I also can see multiple entries of:

     i2c_adapter i2c-0: SMBus collision!
          OR
     i2c_adapter i2c-1: SMBus collision!
          OR
     i2c_adapter i2c-2: SMBus collision!
           OR
     i2c_adapter i2c-3: SMBus collision!
           OR
     i2c_adapter i2c-4: SMBus collision!

This happens with lm_sensors 2.9.2 and 2.10.1 and plain kernel.org kernels
2.6.16.x to 2.6.19.1.

Any idea what is causing this and what I can do to remove the problem?

Thanks,
Holger
-- 

[lm-sensors] LM85 problems with 2.6.16.x - 2.6.19.1

[Philip Pokorny]

Can you send all of the 'lm85' lines from dmesg (ie dmesg | grep lm85) to the list.  I would like to confirm which chip was detected.  We may also need 'i2cdump 0 0x2e'

Thanks,
:v)

 -----Original Message-----
From: 	Holger Kiehl [mailto:Holger.Kiehl at dwd.de]
Sent:	Mon Feb 05 07:11:22 2007
To:	lm-sensors at lm-sensors.org
Subject:	[lm-sensors] LM85 problems with 2.6.16.x - 2.6.19.1

Hello

I am using a Tyan S4882 motherboard with 4 CPU's that has a LM85 sensor chip
which reports the following message during boot:

     .
     .
     ipmi device interface
     Enabling SMBus multiplexing for Tyan S4882
     lm85 0-002e: Client (0,0x2e) config is locked.
     lm85 0-002e: Client (0,0x2e) is not ready.
     lm85 0-002e: Client (0,0x2e) VxI mode is set. Please report this to the lm85 maintainer.

Looking at /var/log/messages I also can see multiple entries of:

     i2c_adapter i2c-0: SMBus collision!
          OR
     i2c_adapter i2c-1: SMBus collision!
          OR
     i2c_adapter i2c-2: SMBus collision!
           OR
     i2c_adapter i2c-3: SMBus collision!
           OR
     i2c_adapter i2c-4: SMBus collision!

This happens with lm_sensors 2.9.2 and 2.10.1 and plain kernel.org kernels
2.6.16.x to 2.6.19.1.

Any idea what is causing this and what I can do to remove the problem?

Thanks,
Holger
-- 



_______________________________________________
lm-sensors mailing list
lm-sensors at lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070205/cc205f2e/attachment.html 

[lm-sensors] LM85 problems with 2.6.16.x - 2.6.19.1

[Holger Kiehl]

On Mon, 5 Feb 2007, Philip Pokorny wrote:

> Can you send all of the 'lm85' lines from dmesg (ie dmesg | grep lm85) to the list.  I would like to confirm which chip was detected.  We may also need 'i2cdump 0 0x2e'
>
dmesg | grep lm85 is not possible because the system is running for a long
time. But doing this on /var/log/messages just provides the following:

    messages.1:Sep 14 12:35:01 athena kernel: lm85 0-002e: Client (0,0x2e) config is locked.
    messages.1:Sep 14 12:35:01 athena kernel: lm85 0-002e: Client (0,0x2e) is not ready.
    messages.1:Sep 14 12:35:01 athena kernel: lm85 0-002e: Client (0,0x2e) VxI mode is set.  Please report this to the lm85 maintainer.
    messages.1:Sep 21 10:37:04 athena kernel: lm85 0-002e: Client (0,0x2e) config is locked.
    messages.1:Sep 21 10:37:04 athena kernel: lm85 0-002e: Client (0,0x2e) is not ready.
    messages.1:Sep 21 10:37:04 athena kernel: lm85 0-002e: Client (0,0x2e) VxI mode is set.  Please report this to the lm85 maintainer.
    messages.1:Sep 25 10:38:38 athena kernel: lm85 0-002e: Client (0,0x2e) config is locked.
    messages.1:Sep 25 10:38:38 athena kernel: lm85 0-002e: Client (0,0x2e) is not ready.
    messages.1:Sep 25 10:38:38 athena kernel: lm85 0-002e: Client (0,0x2e) VxI mode is set.  Please report this to the lm85 maintainer.
    messages.1:Oct 30 10:17:41 athena kernel: lm85 0-002e: Client (0,0x2e) config is locked.
    messages.1:Oct 30 10:17:41 athena kernel: lm85 0-002e: Client (0,0x2e) is not ready.
    messages.1:Oct 30 10:17:41 athena kernel: lm85 0-002e: Client (0,0x2e) VxI mode is set.  Please report this to the lm85 maintainer.
    messages.1:Oct 30 10:29:52 athena kernel: lm85 0-002e: Client (0,0x2e) config is locked.
    messages.1:Oct 30 10:29:52 athena kernel: lm85 0-002e: Client (0,0x2e) is not ready.
    messages.1:Oct 30 10:29:52 athena kernel: lm85 0-002e: Client (0,0x2e) VxI mode is set.  Please report this to the lm85 maintainer.
    messages.1:Nov 22 10:03:03 athena kernel: lm85 0-002e: Client (0,0x2e) config is locked.
    messages.1:Nov 22 10:03:03 athena kernel: lm85 0-002e: Client (0,0x2e) is not ready.
    messages.1:Nov 22 10:03:03 athena kernel: lm85 0-002e: Client (0,0x2e) VxI mode is set.  Please report this to the lm85 maintainer.

I just notice that an identical system which has the same problems does not
show the line "lm85 0-002e: Client (0,0x2e) is not ready", ie:

      lm85 0-002e: Client (0,0x2e) config is locked.
      lm85 0-002e: Client (0,0x2e) VxI mode is set. Please report this to the lm85 maintainer.

Here the i2cdump you asked:

    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: 5e 69 c0 c0 c1 4a 1e 46 38 03 e8 03 34 03 e1 03    ^i???J?F8???4???
    30: ff ff ff 00 00 00 00 00 00 00 00 00 00 27 41 60    .............'A`
    40: fe 00 00 0e 6d 79 7a 86 b6 ca b6 ca b6 ca 81 7f    ?..?myz?????????
    50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4    ????........bbb?
    60: c4 c4 00 00 80 80 80 5a 5a 5a 64 64 64 44 40 00    ??..???ZZZdddD at .
    70: 28 00 28 00 00 00 8b 4c f8 00 00 97 00 00 00 00    (.(...?L?..?....
    80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    b0: 00 00 00 00 00 00 00 00 00 00 00 00 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    ................

Thanks, for the quick responce!

Regards,
Holger

[lm-sensors] LM85 problems with 2.6.16.x - 2.6.19.1

[Jean Delvare]

Hi Holger,

On Mon, 5 Feb 2007 15:09:03 +0000 (GMT), Holger Kiehl wrote:
> Hello
> 
> I am using a Tyan S4882 motherboard with 4 CPU's that has a LM85 sensor chip
> which reports the following message during boot:

Which revision of the S4882 is it?

> 
>      .
>      .
>      ipmi device interface
>      Enabling SMBus multiplexing for Tyan S4882

It looks like you are using both IPMI and regular SMBus at the same
time. I am not an IPMI expert but I suspect it could be the reason of
your problems. What do you use IPMI for? Can you try without it?

>      lm85 0-002e: Client (0,0x2e) config is locked.
>      lm85 0-002e: Client (0,0x2e) is not ready.
>      lm85 0-002e: Client (0,0x2e) VxI mode is set. Please report this to the lm85 maintainer.
> 
> Looking at /var/log/messages I also can see multiple entries of:
> 
>      i2c_adapter i2c-0: SMBus collision!
>           OR
>      i2c_adapter i2c-1: SMBus collision!
>           OR
>      i2c_adapter i2c-2: SMBus collision!
>            OR
>      i2c_adapter i2c-3: SMBus collision!
>            OR
>      i2c_adapter i2c-4: SMBus collision!
> 
> This happens with lm_sensors 2.9.2 and 2.10.1 and plain kernel.org kernels
> 2.6.16.x to 2.6.19.1.

Do these "SMBus collision" messages go away if you stop loading the
i2c-amd756-s4882 driver?

-- 
Jean Delvare

[lm-sensors] LM85 problems with 2.6.16.x - 2.6.19.1

[Holger Kiehl]

Hello Jean

On Tue, 6 Feb 2007, Jean Delvare wrote:

> Hi Holger,
>
> On Mon, 5 Feb 2007 15:09:03 +0000 (GMT), Holger Kiehl wrote:
>> Hello
>>
>> I am using a Tyan S4882 motherboard with 4 CPU's that has a LM85 sensor chip
>> which reports the following message during boot:
>
> Which revision of the S4882 is it?
>
I was unable to locate that. Looked for a long time and I found only one
number right in the corner that says 0400Y, but I don't know if that is the
revision.

>>
>>      .
>>      .
>>      ipmi device interface
>>      Enabling SMBus multiplexing for Tyan S4882
>
> It looks like you are using both IPMI and regular SMBus at the same
> time. I am not an IPMI expert but I suspect it could be the reason of
> your problems. What do you use IPMI for? Can you try without it?
>
Yes, that was it. Just unloading the modules did not work. I had to remove
the IPMI card and now I no longer get those SMBus collision messages and
the message about lm85 being locked and not ready no longer shows up.

I used IPMI to read the log about any system events, like reset button
being pressed, etc. But I found those IPMI cards did not write much
into the log that was of use for me, so it is okay for me to just
remove them. Another reason was that I at first did not know about
the W83627HF watchdog and I wanted to use the one on the IPMI card.
But that did not work, it did not reset my system. I then found the
W83627HF and that worked for me.

>>      lm85 0-002e: Client (0,0x2e) config is locked.
>>      lm85 0-002e: Client (0,0x2e) is not ready.
>>      lm85 0-002e: Client (0,0x2e) VxI mode is set. Please report this to the lm85 maintainer.
>>
>> Looking at /var/log/messages I also can see multiple entries of:
>>
>>      i2c_adapter i2c-0: SMBus collision!
>>           OR
>>      i2c_adapter i2c-1: SMBus collision!
>>           OR
>>      i2c_adapter i2c-2: SMBus collision!
>>            OR
>>      i2c_adapter i2c-3: SMBus collision!
>>            OR
>>      i2c_adapter i2c-4: SMBus collision!
>>
>> This happens with lm_sensors 2.9.2 and 2.10.1 and plain kernel.org kernels
>> 2.6.16.x to 2.6.19.1.
>
> Do these "SMBus collision" messages go away if you stop loading the
> i2c-amd756-s4882 driver?
>
I did not try this since removing the IPMI card solved it.

Many thanks for your help!

Regards,
Holger