On 13/02/08 17:53 +0100, Artur Szymiec wrote: > Hello, > > I have a M2N-SLI Deluxe motherboard and > i'm testing the Jordan Crouse patch > (http://lists.lm-sensors.org/pipermail/lm-sensors/2008-January/022338.html). > Results from running sensors: > > 1st result: > ADT7475-i2c-1-2e > Adapter: SMBus nForce2 adapter at 1c40 > vccp: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM > vcc: +3.27 V (min = +0.00 V, max = +4.28 V) > Chasis 2: 2304 RPM (min = 900 RPM) > fan2: 0 RPM (min = 0 RPM) > fan3: 0 RPM (min = 0 RPM) > fan4: 0 RPM (min = 0 RPM) > remote1: FAULT (low = -63.0?C, high = +191.0?C) ALARM > local: +42.5?C (low = +10.0?C, high = +45.0?C) > remote2: FAULT (low = -63.0?C, high = +191.0?C) ALARM > > 2nd result: > ADT7475-i2c-1-2e > Adapter: SMBus nForce2 adapter at 1c40 > vccp: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM > vcc: +3.27 V (min = +0.00 V, max = +4.28 V) > Chasis 2: 105882 RPM (min = 900 RPM) > fan2: 0 RPM (min = 0 RPM) > fan3: 0 RPM (min = 0 RPM) > fan4: 0 RPM (min = 0 RPM) > remote1: FAULT (low = -63.0?C, high = +191.0?C) ALARM > local: +42.5?C (low = +10.0?C, high = +45.0?C) > remote2: FAULT (low = -63.0?C, high = +191.0?C) ALARM > > Comment: > The results 1 and 2 are from running the sensors command one by one > with 3 sec delay between them. > So obviously reading from fan1 (label Chassis 2) are not correct. > Tested with kernel 2.6.24. Thats unfortunate. Is the problem easily reproducible? Does the bogus fan value remain forever or does it go back to a sane value on the next read? Jordan -- Jordan Crouse Systems Software Development Engineer Advanced Micro Devices, Inc.
