Bug 577469 - Slight display issue with memory SPD display.
Summary: Slight display issue with memory SPD display.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: memtest86+
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anton Arapov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-27 09:15 UTC by Maciej Żenczykowski
Modified: 2014-06-18 08:02 UTC (History)
2 users (show)

Fixed In Version: memtest86+-4.00-4.fc13
Clone Of:
Environment:
Last Closed: 2010-06-15 16:03:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Maciej Żenczykowski 2010-03-27 09:15:28 UTC
I have a stick of "Mushkin 991587 (996587)" memory.
It is correctly identified as such by modprobe eeprom; decode-dimms.
A manual dump "i2cdump 0 0x50 b" confirms this.

However, memtest86+ shows:

Memory SPD Informations
--------------------------
  - Slot 0 : 2048 MB DDR2-400 - Mushkin 99158  (99658 )

ie. the 7's have magically become spaces.

Comment 1 Maciej Żenczykowski 2010-03-27 09:17:41 UTC
memtest86+-4.00-2.fc12.x86_64

Comment 2 Anton Arapov 2010-03-29 09:00:50 UTC
Maciej, thanks for the report and could you attach the output of the "dmidecode --dump-bin" here?

Comment 3 Maciej Żenczykowski 2010-03-29 18:22:44 UTC
[root@zeus ~]# dmidecode 
# dmidecode 2.10
# No SMBIOS nor DMI entry point found, sorry.

[root@zeus ~]# decode-dimms 
# decode-dimms version 5388 (2008-11-18 18:15:09 +0100)

Memory Serial Presence Detect Decoder
By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner,
Jean Delvare, Trent Piepho and others


Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0050
Guessing DIMM is in                             bank 1

---=== SPD EEPROM Information ===---
EEPROM Checksum of bytes 0-62                   OK (0xF5)
# of bytes written to SDRAM EEPROM              128
Total number of bytes in EEPROM                 256
Fundamental Memory type                         DDR2 SDRAM
SPD Revision                                    1.2

---=== Memory Characteristics ===---
Maximum module speed                            800MHz (PC2-6400)
Size                                            2048 MB
Banks x Rows x Columns x Bits                   8 x 14 x 10 x 64
Ranks                                           2
SDRAM Device Width                              8 bits
Module Height                                   30.0 mm
Module Type                                     UDIMM (133.25 mm)
DRAM Package                                    Planar
Voltage Interface Level                         SSTL 1.8V
Refresh Rate                                    Reduced (7.8 us) - Self Refresh
Supported Burst Lengths                         4, 8
tCL-tRCD-tRP-tRAS                               5-4-4-12
Supported CAS Latencies (tCL)                   5T, 4T
Minimum Cycle Time at CAS 5 (tCK min)           2.50 ns
Maximum Access Time at CAS 5 (tAC)              0.40 ns
Minimum Cycle Time at CAS 4                     3.75 ns
Maximum Access Time at CAS 4                    0.50 ns
Maximum Cycle Time (tCK max)                    8.00 ns

---=== Timing Parameters ===---
Address/Command Setup Time Before Clock (tIS)   0.17 ns
Address/Command Hold Time After Clock (tIH)     0.25 ns
Data Input Setup Time Before Strobe (tDS)       0.05 ns
Data Input Hold Time After Strobe (tDH)         0.12 ns
Minimum Row Precharge Delay (tRP)               10.00 ns
Minimum Row Active to Row Active Delay (tRRD)   7.50 ns
Minimum RAS# to CAS# Delay (tRCD)               10.00 ns
Minimum RAS# Pulse Width (tRAS)                 30.00 ns
Write Recovery Time (tWR)                       15.00 ns
Minimum Write to Read CMD Delay (tWTR)          7.50 ns
Minimum Read to Pre-charge CMD Delay (tRTP)     7.50 ns
Minimum Active to Auto-refresh Delay (tRC)      60.00 ns
Minimum Recovery Delay (tRFC)                   127.50 ns
Maximum DQS to DQ Skew (tDQSQ)                  0.20 ns
Maximum Read Data Hold Skew (tQHS)              0.30 ns

---=== Manufacturing Information ===---
Manufacturer                                    Mushkin
Manufacturing Location Code                     0x01
Part Number                                     991587 (996587)
Manufacturing Date                              0x070B


Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0052
Guessing DIMM is in                             bank 3


---=== SPD EEPROM Information ===---
EEPROM Checksum of bytes 0-62                   OK (0xF5)
# of bytes written to SDRAM EEPROM              128
Total number of bytes in EEPROM                 256
Fundamental Memory type                         DDR2 SDRAM
SPD Revision                                    1.2

---=== Memory Characteristics ===---
Maximum module speed                            800MHz (PC2-6400)
Size                                            2048 MB
Banks x Rows x Columns x Bits                   8 x 14 x 10 x 64
Ranks                                           2
SDRAM Device Width                              8 bits
Module Height                                   30.0 mm
Module Type                                     UDIMM (133.25 mm)
DRAM Package                                    Planar
Voltage Interface Level                         SSTL 1.8V
Refresh Rate                                    Reduced (7.8 us) - Self Refresh
Supported Burst Lengths                         4, 8
tCL-tRCD-tRP-tRAS                               5-4-4-12
Supported CAS Latencies (tCL)                   5T, 4T
Minimum Cycle Time at CAS 5 (tCK min)           2.50 ns
Maximum Access Time at CAS 5 (tAC)              0.40 ns
Minimum Cycle Time at CAS 4                     3.75 ns
Maximum Access Time at CAS 4                    0.50 ns
Maximum Cycle Time (tCK max)                    8.00 ns

---=== Timing Parameters ===---
Address/Command Setup Time Before Clock (tIS)   0.17 ns
Address/Command Hold Time After Clock (tIH)     0.25 ns
Data Input Setup Time Before Strobe (tDS)       0.05 ns
Data Input Hold Time After Strobe (tDH)         0.12 ns
Minimum Row Precharge Delay (tRP)               10.00 ns
Minimum Row Active to Row Active Delay (tRRD)   7.50 ns
Minimum RAS# to CAS# Delay (tRCD)               10.00 ns
Minimum RAS# Pulse Width (tRAS)                 30.00 ns
Write Recovery Time (tWR)                       15.00 ns
Minimum Write to Read CMD Delay (tWTR)          7.50 ns
Minimum Read to Pre-charge CMD Delay (tRTP)     7.50 ns
Minimum Active to Auto-refresh Delay (tRC)      60.00 ns
Minimum Recovery Delay (tRFC)                   127.50 ns
Maximum DQS to DQ Skew (tDQSQ)                  0.20 ns
Maximum Read Data Hold Skew (tQHS)              0.30 ns

---=== Manufacturing Information ===---
Manufacturer                                    Mushkin
Manufacturing Location Code                     0x01
Part Number                                     991587 (996587)
Manufacturing Date                              0x070B



Number of SDRAM DIMMs detected and decoded: 2


[root@zeus ~]# i2cdump -y 0 0x50
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 80 08 08 0e 0a 61 40 00 05 25 40 00 82 08 00 00    ?????a@.?%@.??..
10: 0c 08 30 01 02 00 07 3d 50 00 00 28 1e 28 1e 01    ??0??.?=P..(?(??
20: 17 25 05 12 3c 1e 1e 00 06 3c 7f 80 14 1e 00 00    ?%??<??.?<????..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 f5    ..............??
40: 7f 7f 7f 94 ff ff ff ff 01 39 39 31 35 38 37 20    ????....?991587 
50: 28 39 39 36 35 38 37 29 00 00 00 00 00 07 0b 00    (996587).....??.
60: 00 00 00 6d 56 4e a1 10 80 25 20 28 28 1e 00 00    ...mVN???% ((?..
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

[root@zeus ~]# i2cdump -y 0 0x52
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 80 08 08 0e 0a 61 40 00 05 25 40 00 82 08 00 00    ?????a@.?%@.??..
10: 0c 08 30 01 02 00 07 3d 50 00 00 28 1e 28 1e 01    ??0??.?=P..(?(??
20: 17 25 05 12 3c 1e 1e 00 06 3c 7f 80 14 1e 00 00    ?%??<??.?<????..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 f5    ..............??
40: 7f 7f 7f 94 ff ff ff ff 01 39 39 31 35 38 37 20    ????....?991587 
50: 28 39 39 36 35 38 37 29 00 00 00 00 00 07 0b 00    (996587).....??.
60: 00 00 00 6d 56 4e a1 10 80 25 20 28 28 1e 00 00    ...mVN???% ((?..
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

(and yes, the machine in question actually has 2 dimms, and both show the same issue in memtest, except the second is listed with a different slot number (either '1' or '2', I think '1')

[Further note, I've rewritten the SPD timings to 5-4-4-12 (manufacturer supported for this DIMM, both on website and on dimm label) from 5-5-5-18 (jedec standard, shipped with these values in SPD), but the problem was there even before this]

for CHIP in 0x50 0x52; do
  # tRCD
  i2cget -y 0 ${CHIP} 29 b; # 0x32 * 0.25 ns == 12.5 ns (5 cycles @ 2.5ns)
  i2cset -y 0 ${CHIP} 29 0x28 b; # * 0.25 ns == 10.0 ns (4 cycles @ 2.5ns)

  # tRP
  i2cget -y 0 ${CHIP} 27 b; # 0x32 * 0.25 ns == 12.5 ns (5 cycles @ 2.5ns)
  i2cset -y 0 ${CHIP} 27 0x28 b; # * 0.25 ns == 10.0 ns (4 cycles @ 2.5ns)

  # tRAS
  i2cget -y 0 ${CHIP} 30 b; # 0x2D * 1.00 ns == 45.0 ns (18 cycles @ 2.5ns)
  i2cset -y 0 ${CHIP} 30 0x1E b; # * 1.00 ns == 30.0 ns (12 cycles @ 2.5ns)

  # SPD checksum
  i2cget -y 0 ${CHIP} 63 b; # 0x18 is the old checksum
  # (0x18 - 0x32 + 0x28 - 0x32 + 0x28 - 0x2d + 0x1E) & 0xFF == 0xF5
  i2cset -y 0 ${CHIP} 63 0xF5 b; # is the new checksum
done

Comment 4 Anton Arapov 2010-03-30 09:33:17 UTC
Maciej,

  please test the following package if it fixes your problem:

- x86_64:
http://koji.fedoraproject.org/koji/getfile?taskID=2083725&name=memtest86%2B-4.00-3.fc12.x86_64.rpm
- i686:
http://koji.fedoraproject.org/koji/getfile?taskID=2083726&name=memtest86%2B-4.00-3.fc12.i686.rpm

complete build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2083722

it has the following fix inside:
 spd.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/spd.c b/spd.c
index 0cdfe1e..b99dd90 100644
--- a/spd.c
+++ b/spd.c
@@ -481,6 +481,7 @@ struct ascii_map amap[] = {
 { 0x34, "4"},
 { 0x35, "5"},
 { 0x36, "6"},
+{ 0x37, "7"},
 { 0x38, "8"},
 { 0x39, "9"},
 { 0x3A, ":"},

I don't know the reason why 0x37 was omitted... :/ hopefully, it won't hurt anybody.

Comment 5 Anton Arapov 2010-04-01 13:34:28 UTC
Maciej, have you had a chance to test it?

Comment 6 Maciej Żenczykowski 2010-04-01 18:44:06 UTC
No, I haven't, will try this weekend when I can reboot the machine.

Comment 7 Maciej Żenczykowski 2010-04-02 09:20:09 UTC
Confirmed to be fixed in:
memtest86+-4.00-3.fc12.x86_64

Comment 8 Anton Arapov 2010-04-02 12:01:39 UTC
ok... going to push it f12/f13/rawhide then.

Comment 9 Fedora Update System 2010-04-02 12:27:56 UTC
memtest86+-4.00-3.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/memtest86+-4.00-3.fc12

Comment 10 Fedora Update System 2010-04-02 12:28:44 UTC
memtest86+-4.00-4.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/memtest86+-4.00-4.fc13

Comment 11 Fedora Update System 2010-04-02 18:43:28 UTC
memtest86+-4.00-4.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update memtest86+'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/memtest86+-4.00-4.fc13

Comment 12 Maciej Żenczykowski 2010-04-02 23:46:26 UTC
# rpm -q memtest86+
memtest86+-4.00-3.fc12.x86_64
# rm -rf /var/cache/yum/x86_64/12/updates-testing
# yum --enablerepo=updates-testing update memtest86+
Loaded plugins: dellsysidplugin2, refresh-packagekit
updates-testing/metalink                                 |  14 kB     00:00     
updates-testing                                          | 4.4 kB     00:00     
updates-testing/primary_db                               | 898 kB     00:00     
Setting up Update Process
No Packages marked for Update

I don't know, I never seem to have any luck with updates-testing.

Comment 13 Fedora Update System 2010-04-03 04:38:58 UTC
memtest86+-4.00-3.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update memtest86+'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/memtest86+-4.00-3.fc12

Comment 14 Anton Arapov 2010-05-03 09:02:09 UTC
issue has raised upstream:
  - http://forum.canardpc.com/showthread.php?t=46127

Comment 15 Anton Arapov 2010-05-05 08:21:32 UTC
(In reply to comment #14)
has been accepted, should appear in v4.11 of upstream.

Comment 16 Fedora Update System 2010-06-15 16:03:12 UTC
memtest86+-4.00-4.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.