LM85 problems with 2.6.16.x - 2.6.19.1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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




[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux