If i2cdump reports 00 but the adm1025 driver reports 65535 that would suggest that the adm1025 driver _is_ the problem. Kevin Flasch wrote: > > > On Fri, 19 Apr 2002, Mark D. Studebaker wrote: > > > > > One thing you can do is use 'prog/dump/i2cdump 0 0x2d' > > > to dump the registers of the chip. > > > Look for either FF at the alarm registers at 0x41 and 0x42, > > > or maybe all FF's. > > > This will eliminate the adm1025 driver as the problem. > > > > I'm monitoring this on a machine now. When I have results, I will email you > > them. > > Hi. I have some results. I don't want to run i2cdump on the entire cluster of > machines I have because of the warning it outputs. I have run it on one > machine and got a few reults suggesting that the adm1025 driver is not the > problem. When alarms hits 65535, i2cdump reports > > 40: 01 00 00 5b 5b 5b 5b 07 5b 80 5b 5b 5b 5b 5b 5b > > which is what it normally reports. I'll keep monitoring this and get more > results. > > ---------------------------------------- > Kevin James Flasch > http://www.uwm.edu/~kflasch/kflasch.gpg
