Serial presence detect (SPD) refers to a standardized way to automatically access information about a computer memory module.
You have a problem with the memory module DIMM1. From my experience with PC's you can live with this long time or in the worst case after a reboot the memory DIMM1 will be deconfigured.
On the CX4-240 messages include DIMM modules 2 and 3:
B 10/03/09 06:37:02 71324001 SMBus read failed for device Local SPD DIMM2. Failure occurred at I2C addr 0xAC after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
B 10/03/09 06:37:02 71324001 SMBus read failed for device Local SPD DIMM3. Failure occurred at I2C addr 0xA4 after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
A 10/03/09 07:06:01 71324001 SMBus read failed for device Local SPD DIMM2. Failure occurred at I2C addr 0xAC after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
A 10/03/09 07:06:01 71324001 SMBus read failed for device Local SPD DIMM3. Failure occurred at I2C addr 0xA4 after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
The messages are benign and can be ignored. Messages will be logged every 80 hours (approximately) after 28800 polling attempts are performed every 10 seconds. The SMBus is being erroneously polled for memory modules that do not exist for the CX4-120 and CX4-240 platforms.
Fix:
The issue will be fixed in a future release of FLARE after Release 29.
Workaround:
In the monitoring section in Navisphere, select the template that the CLARiiON is using. Select properties of the template (the template should already be using explicit events) and select Advanced. In the sections Warning -> Basic Array Features make sure that 0x71324001 is deselected.
The issue has been resolved in the yet to be released Release 30. There are no plans to patch Release 29 for this issue at this point in time (July 2010).
If you have a CX4-120 running Release 29 then the Fix is ...
The issue will be fixed in a future release of FLARE after Release 29.
Workaround:
In the monitoring section in Navisphere, select the template that the CLARiiON is using. Select properties of the template (the template should already be using explicit events) and select Advanced. In the sections Warning -> Basic Array Features make sure that 0x71324001 is deselected.
FNP
4 Posts
0
September 2nd, 2010 00:00
Serial presence detect (SPD) refers to a standardized way to automatically access information about a computer memory module.
You have a problem with the memory module DIMM1. From my experience with PC's you can live with this long time or in the worst case after a reboot the memory DIMM1 will be deconfigured.
Roops1
18 Posts
0
September 2nd, 2010 01:00
Hi,
Please check below primus EMC 222703 will give you idea about this SMBus read failed warning.
Please mark it answered if this answer your query.
On the CX4-120 messages include DIMM modules 1 and 3:
B 09/07/09 05:53:13 71324001 SMBus read failed for device Local SPD DIMM1. Failure occurred at I2C addr 0xA6 after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
B 09/07/09 05:53:13 71324001 SMBus read failed for device Local SPD DIMM3. Failure occurred at I2C addr 0xA4 after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
A 09/07/09 06:36:04 71324001 SMBus read failed for device Local SPD DIMM1. Failure occurred at I2C addr 0xA6 after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
A 09/07/09 06:36:05 71324001 SMBus read failed for device Local SPD DIMM3. Failure occurred at I2C addr 0xA4 after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
On the CX4-240 messages include DIMM modules 2 and 3:
B 10/03/09 06:37:02 71324001 SMBus read failed for device Local SPD DIMM2. Failure occurred at I2C addr 0xAC after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
B 10/03/09 06:37:02 71324001 SMBus read failed for device Local SPD DIMM3. Failure occurred at I2C addr 0xA4 after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
A 10/03/09 07:06:01 71324001 SMBus read failed for device Local SPD DIMM2. Failure occurred at I2C addr 0xAC after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
A 10/03/09 07:06:01 71324001 SMBus read failed for device Local SPD DIMM3. Failure occurred at I2C addr 0xA4 after 28800 unsuccessful attempts. Device error. 00000400 05005000 d3040000 014032a1 014032a1 00000000 00000000 00000000 00000000 00000000 71324001 SMBus
The issue will be fixed in a future release of FLARE after Release 29.
Workaround:
In the monitoring section in Navisphere, select the template that the CLARiiON is using. Select properties of the template (the template should already be using explicit events) and select Advanced. In the sections Warning -> Basic Array Features make sure that 0x71324001 is deselected.
Parks2
116 Posts
1
September 2nd, 2010 05:00
If you have a CX4-120 running Release 29 then the Fix is ...
The issue will be fixed in a future release of FLARE after Release 29.
Workaround:
In the monitoring section in Navisphere, select the template that the CLARiiON is using. Select properties of the template (the template should already be using explicit events) and select Advanced. In the sections Warning -> Basic Array Features make sure that 0x71324001 is deselected.
Jim_A1
59 Posts
0
September 7th, 2010 21:00
Nel, the fix is in a FUTURE release of R29.
Unfortunatly the only way to stop this error before the next patch of R29 is released, is to do the workaround.
nal2
2 Posts
0
September 7th, 2010 21:00
The Array in question is on Flare 29. However disabling the warning is not acceptable to the customer. Have raised an SR, & awaiting further advice.
urgently
11 Posts
0
April 8th, 2012 06:00
actually i have this issue running at CX4-120 and i'm going to do code upgrade and check the status after code upgrade to Release