Hi Rudolf
> Lets try to solve this. Best would be to grab you DDR module put it to
> other machine with some other than ali SMBUS controller and do the
dump
> again. If it is same, eeprom is really corrupted. If it differs send
it
> here please.
(1)
First, I use other two ECC RAMs(ECC PC2100) to substitute my original
ECC PC1600R memory, find that the problem still appears on ABIT SU-2S
with
ALI M1563:
[root@ ~]# modprobe eeprom
[root@ ~]# sensors
eeprom-i2c-0-51
Adapter: SMBus ALi 1563 Adapter @ 5000
Unknown EEPROM type (255).
eeprom-i2c-0-50
Adapter: SMBus ALi 1563 Adapter @ 5000
Unknown EEPROM type (255).
w83792d-i2c-0-2f
Adapter: SMBus ALi 1563 Adapter @ 5000
VCoreA: +1.52 V (min = +0.00 V, max = +1.78 V)
.................. /* some lines omitted here */
(2)
Then I move memory(ECC PC2100) and harddisk to another machine without
ALI M1563:
RIOWORKS PDPLA0250000005
Intel Corp.82801CA/CAM SMBus Controller
Intel(R) XEON(TM) CPU 2.00GHz
find that the eeprom works well, please refer to the following message.
[root@ ~]# modprobe eeprom
[root@ ~]# sensors
eeprom-i2c-0-54
Adapter: SMBus I801 adapter at 1100
Memory type: DDR SDRAM DIMM
Memory size (MB): 128
eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 1100
Memory type: DDR SDRAM DIMM
Memory size (MB): 128
(3)
> Second and more likely is that ALI smbus host or our driver has some
> problem.
> Please can you try
> i2cdump 0 0x50 c
> This will use other SMBUS commands for readings maybe this time we
will
> get something better.
I move the harddisk and memory back to the ABit motherboard with ALi
M1563,
#modprobe eeprom
Please refer to log message1 in attachment
(4) classic i2dump, please refer to log message2 in attachment
[root@ ~]# i2cdump 0 0x50
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 0x50, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 00 07 0c 0a 01 48 00 04 75 75 02 80 08 08 01 ..????H.?uu?????
10: 0e 04 0c 01 02 26 00 a0 75 00 00 50 3c 50 30 20 ?????&.?u..P<P0
20: 00 00 50 50 00 00 00 00 00 41 4b 30 32 75 00 00 ..PP.....AK02u..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1a ...............?
40: 00 00 00 00 00 00 00 bb ff 00 00 00 00 00 00 00 .......?........
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
c0: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: 00 00 ac ff ff ff ff ff ff ff ff ff ff ff ff ff ..?.............
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
(5) i2cdump with c, please refer to log message3 in attachment
[root@ ~]# i2cdump 0 0x50 c
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-0, address 0x50, mode byte consecutive read
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
Btw:
My motherboard ABit SU-2S supports dual channel DDR 400/333 memory,
while the memory I'm using is DDR266/PC2100.
Does it have something to do with our problem?
Thanks
Best Regards
Chunhao
===========================================================================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original author of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such person, please kindly reply the sender indicating accordingly and delete all copies of it from your computer and network server immediately. We thank you for your cooperation. It is advisable that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email that does not relate to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.===========================================================================================If your computer is unable to decode Chinese font, please ignore the following message. They essentially repeat the English statement above.???H???????t?????q?l???]???????K?????T, ?????v???o?H?H???w?????H?H???\????. ?????z???D?Q???w?????H?H???]???????]?b???g???v?????????U???????H??, ???z?i?????o?H?H?????Y?N?H???q?q???P???????A???????H????. ?????z???X?@, ?????????P??. ?S??????, ???????g???v?????????????q?l?????K???T???????O?Q?Y???T????. ?H???P?????q?l???~?L???????e,???o?????????q?l?????????N??.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debug_log.tar.gz
Type: application/x-gzip
Size: 15609 bytes
Desc: debug_log.tar.gz
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20050330/8bfffc49/attachment.gz
