Sun Fire Servers May not Report the Correct DIMM Location after Dynamic Reconfiguration (DR) Event

---

Impact

On Sun Fire servers, after unconfiguring a system board that experienced Correctable Error (CE) messages, the DIMM location may be reported incorrectly or may be just a blank space. This issue could result in unnecessary hardware replacement.

Contributing Factors

This issue can occur in the following releases:

SPARC

• Solaris 8 without patch 109888-19
• Solaris 9 without patch 114359-01

on the following platforms:

• Sun Fire 12K
• Sun Fire 15K
• Sun Fire Servers (3800/4800/4810/6800)

This issue only occurs if all of the following conditions are true:

1. A DR suspend-resume (a.k.a. copy-rename) has occurred, and
2. Correctable Errors (CE) have occurred on the target system board of the DR suspend-resume (due to faulty hardware or other rare conditions), and
3. The target of the DR suspend-resume will have permanent memory, see cfgadm(1M) to verify that the system board in question has permanent memory.

Note: Solaris 2.6 and 7 are not affected.

Symptoms

The following CE message (displayed on the console) does not show a DIMM location:

	[AFT0] Corrected system bus (CE) Event on CPU3 at TL=0, errID 0x0000052c.3c0bb98a
	AFSR 0x00000002<CE>.00000098 AFAR 0x00000003.bc769130 Fault_PC 0x100033b88 Esynd 0x0098
	[AFT0] errID 0x0000052c.3c0bb98a Corrected Memory Error on   is Persistent
	[AFT0] errID 0x0000052c.3c0bb98a Data Bit 114 was in error and corrected

The DIMM location may also be reported incorrectly.

Workaround

To work around the described issue, reboot the system and do not perform any subsequent suspend-resume operations.

Resolution

This issue is addressed in the following releases:

SPARC Platform

• Solaris 8 with patch 109888-19 or later
• Solaris 9 with patch 114359-01 or later

Modification History


Date: 24-FEB-2003

• Updated Contributing Factors, Relief/Workaround and Resolution sections

Date: 06-MAR-2003

• State: Resolved (and Closed)
• Updated Contributing Factors, Relief/Workaround and Resolution sections

Attachments

This solution has no attachment