Hello all, > > this appears simply a probing for non-existent i2c ports (correct me if I am > wrong) presumably by eeprom driver. yes I think you are right. (ADD/2 is the address of chip, that it tries to access) > Second block are errors from lm90 for different registers: > > Jan 15 22:24:02 cooker kernel: i2c_adapter i2c-0: Transaction (pre): STS=04, > TYP=10, CMD=01, ADD=99, DAT0=a0, DAT1=10 > Jan 15 22:24:02 cooker kernel: i2c_adapter i2c-0: Transaction (post): STS=14, > TYP=10, CMD=01, ADD=99, DAT0=29, DAT1=10 > Jan 15 22:24:02 cooker kernel: i2c_adapter i2c-0: Transaction (pre): STS=04, > TYP=10, CMD=08, ADD=98, DAT0=29, DAT1=10 > Jan 15 22:24:02 cooker kernel: i2c_adapter i2c-0: Error: command never > completed > Jan 15 22:24:02 cooker kernel: i2c_adapter i2c-0: Transaction (post): STS=04, > TYP=10, CMD=08, ADD=98, DAT0=29, DAT1=10 > Jan 15 22:24:02 cooker kernel: lm90 0-004c: Register 0x8 read failed (-1) > Jan 15 22:24:02 cooker kernel: i2c_adapter i2c-0: Transaction (pre): STS=04, > TYP=10, CMD=07, ADD=98, DAT0=29, DAT1=10 > Jan 15 22:24:02 cooker kernel: i2c_adapter i2c-0: Transaction (post): STS=14, > TYP=10, CMD=07, ADD=98, DAT0=29, DAT1=10 > > Here I do not see SMBus errors - it appears really that i2c device did not > respond. OTOH interesting is that there is no timeout. Apparently command > completed without setting DONE bit. As I have zero knowledge about hardware I > cannot interpret it. Next driver resets SMBus and it works for some time > again. Judging by comments in source, it apprently signifies hung ali1535, > not external i2c device (it is using KILL, and "this doesn't seem to clear > the controller if an external device is hung") Well it seems this ali 15x3 has maybe same hardware bug? It was mentioned already here: http://www2.lm-sensors.nu/~lm78/readticket.cgi?ticket=2030 > In the log below you can see that the ALI15X3 chip seems to keep in idle-state > without reporting "done", but it does not turn in "busy" state. I patched the > driver to do the reset procedure (with ALI15X3_T_OUT) after the error, but > afterwards, the chip turns to "busy" state until next reboot. And it continued: http://lists.lm-sensors.org/pipermail/lm-sensors/2005-October/013808.html I asked for a patch and what I have received like a month after is patch that works for them: > Dear Rudolf, > > unfortunately i do not have cvs installed on my machine. I hope it's okay if > i send you the complete patched module (the only file i changed was the > i2c-ali15x3.c) so you can do the patch yourself. Since i'm not a experienced > driver developer i do not know what you ment with your last sentence and i > did not find any remarks on the website. > > However, feel free to contact me if you have still any questions. > > This version works fine and without any problems over many days in our test > system. > > Regards, > Claudio Klingler I'm putting it into attachment. (this is against the lmsensors CVS so 2.4 driver) Since I dont own the motherboard with this chip (nor the datasheet) and the resulting driver was hard to read I just left this issue. I hope it can help now. Regards Rudolf -------------- next part -------------- A non-text attachment was scrubbed... Name: i2c-ali15x3.c Type: text/x-csrc Size: 16990 bytes Desc: not available Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060115/0b2bfd6b/attachment.bin
