Information in this document applies to any platform.
SUNBUG:7119934
Date of Workaround Release: 09-May-2012
Date of Resolved Release: 25-May-2012
___________________________________
Description
SPARC and Netra T3/T4 systems (listed below) running firmware prior to 8.2.0.a could report a "VCORE_POK_GLITCH" error, followed by a system shutdown.
Occurrence
This issue can occur on the following platforms:
SPARC Platform:
- SPARC T3-1, T3-2, T3-4, T3-1B
- SPARC T4-1, T4-2, T4-4, T4-1B
- SPARC Netra T3-1, T3-1B, T4-1, T4-2, T4-1B
when running system firmware prior to version 8.2.0.a.
Please also see the "Workaround" section below for information regarding LDOMs 2.1 and 2.2 and associated patches for firmware 8.1.5.
Notes:
1. No x86 platform systems are affected by this issue.
2. Only the systems listed above running firmware prior to release 8.2.0.a are affected by this issue.
To determine the current firmware version on a system, the following command can be run:
From ILOM:
-> show HOST
From Solaris:
% prtdiag -v
Symptoms
Systems that experience this issue will see the following message under the SP (Service Processor) FMA "Ereport" prior to the system shutting down:
ereport.chassis.power.glitch-fatal@/sys/mb /SYS/MB/CMP0/VCORE_POK_GLITCH
Workaround
There is no workaround for this issue.
This issue is addressed in the following releases:
SPARC Platform
- SPARC T3-1 with System Firmware version 8.2.0.a (as delivered in patch 148816-01) or later
- SPARC T3-2 with System Firmware version 8.2.0.a (as delivered in patch 148817-01) or later
- SPARC T3-4 with System Firmware version 8.2.0.a (as delivered in patch 148818-01) or later
- SPARC T3-1B with System Firmware version 8.2.0.a (as delivered in patch 148819-01) or later
- Netra T3-1 with System Firmware version 8.2.0.a (as delivered in patch 148820-01) or later
- SPARC T4-1 with System Firmware version 8.2.0.a (as delivered in patch 148822-01) or later
- SPARC T4-2 with System Firmware version 8.2.0.a (as delivered in patch 148823-01) or later
- SPARC T4-4 with System Firmware version 8.2.0.a (as delivered in patch 148824-01) or later
- SPARC T4-1B with System Firmware version 8.2.0.a (as delivered in patch 148825-01) or later
- Netra T3-1B with System Firmware version 8.2.0.a (as delivered in patch 148821-01) or later
- Netra T4-1 with System Firmware version 8.2.0.a (as delivered in patch 148826-01) or later
- Netra T4-2 with System Firmware version 8.2.0.a (as delivered in patch 148827-01) or later
- Netra T4-1B with System Firmware version 8.2.0.a (as delivered in patch 148828-01 ) or later
Note: The patches listed above for firmware 8.2.0.a apply to systems running both Logical Domain Manager (LDOM) 2.1. and LDOM 2.2.
For systems running LDOM 2.1, the following firmware patches address this issue, however, upgrading to firmware 8.2.0.a is recommended:
- SPARC T3-1 with System Firmware version 8.1.5 (as delivered in patch 147315-06) or later
- SPARC T3-2 with System Firmware version 8.1.5 (as delivered in patch 147316-06) or later
- SPARC T3-4 with System Firmware version 8.1.5 (as delivered in patch 147317-06) or later
- SPARC T3-1B with System Firmware version 8.1.5 (as delivered in patch 147318-05) or later
- Netra T3-1 with System Firmware version 8.1.5 (as delivered in patch 147319-07) or later
- Netra T3-1B with System Firmware version 8.1.5 (as delivered in patch 147320-05) or later
- SPARC T4-1 with System Firmware version 8.1.5 (as delivered in patch 147284-04) or later
- SPARC T4-2 with System Firmware version 8.1.5 (as delivered in patch 147285-04) or later
- SPARC T4-4 with System Firmware version 8.1.5 (as delivered in patch 147286-05) or later
- SPARC T4-1B with System Firmware version 8.1.5 (as delivered in patch 147287-04) or later
- Netra T4-1 with System Firmware version 8.1.5 (as delivered in patch 147289-04) or later
- Netra T4-1B with System Firmware version 8.1.5 (as delivered in patch 147291-05) or later
- Netra T4-2 with System Firmware version 8.1.5 (as delivered in patch 147290-03) or later
Patches
<SUNPATCH:147315-06> <SUNPATCH:148816-01>
<SUNPATCH:147316-06> <SUNPATCH:148817-01>
<SUNPATCH:147317-06> <SUNPATCH:148818-01>
<SUNPATCH:147318-05> <SUNPATCH:148819-01>
<SUNPATCH:147319-07> <SUNPATCH:148820-01>
<SUNPATCH:147320-05> <SUNPATCH:148821-01>
<SUNPATCH:147284-04> <SUNPATCH:148822-01>
<SUNPATCH:147285-04> <SUNPATCH:148823-01>
<SUNPATCH:147286-05> <SUNPATCH:148824-01>
<SUNPATCH:147287-04> <SUNPATCH:148825-01>
<SUNPATCH:147289-04> <SUNPATCH:148826-01>
<SUNPATCH:147290-03> <SUNPATCH:148827-01>
<SUNPATCH:147291-05> <SUNPATCH:148828-01>
History
09-May-2012: Document created, Workaround release
10-May-2012: Add Netra T3-1B, add BugIDs
11-May-2012: Final edits and maintenance
25-May-2012: Patches released, issue is Resolved
30-May-2012: Correction to typo error in Workaround (FW 8.2.0.a)
09-Aug-2012: Updated to include patches for firmware 8.1.5
14-Sep-2012: Maintenance update
Note to Support: A hardware tolerance issue has increased incidents of "false positives" of the VCORE_POK glitch on these systems. Firmware rev 8.1.5 or later stops these false positives. But if a Customer sees this VCORE on a system with sysfw 8.1.5 or higher, they could have a failed DCDC (D220) converter which requires troubleshooting and diagnostic procedures outside the scope of this Sun Alert.
Also Note: All other POK glitches different from false positive VCORE, such as DC_POK, IO_POK, etc. are not addressed by Firmware rev 8.1.5 or later. Normal troubleshooting procedures should be followed for those failures.
Please send technical questions to:
[email protected]
and copy the Responsible Engineer/Contributor listed
Internal Contributor/Submitter: [email protected]
Internal Eng Responsible Engineer: [email protected]
Internal Services Knowledge Engineer: [email protected]
Internal Eng Business Unit Group:Systems Group-Netra Systems and Networking
Systems Group-SVS (SPARC Volume Systems, Horizontal Systems,(includes T2000/Ontario)
Internal Escalation ID: 3-4768603031, 3-4768443911
Internal Resolution Patches: listed in body content and references sections
References
SUNBUG:7119934
Attachments
This solution has no attachment