T3-x/T4-x systems might report "Speed mismatch detected, Invalid processor speed, Failed to margin" events after a MB and/or PM replacement during POST

Asset ID:	1-72-1587745.1
Update Date:	2017-12-13
Keywords:

Solution Type Problem Resolution Sure

Solution 1587745.1 : T3-x/T4-x systems might report "Speed mismatch detected, Invalid processor speed, Failed to margin" events after a MB and/or PM replacement during POST

Applies to:

SPARC T4-4 - Version All Versions to All Versions [Release All Releases]
SPARC T4-2 - Version All Versions to All Versions [Release All Releases]
SPARC T4-1 - Version All Versions to All Versions [Release All Releases]
SPARC T3-4 - Version All Versions to All Versions [Release All Releases]
SPARC T3-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

After replacement of a MotherBoard (MB) and/or ProcessorModule (PM) due to a failure, the new MB and/or PM might contain a higher T3/T4 CPU revision and might report the following failures:

- MB
- ERROR: Speed mismatch detected.
- ERROR: Failed to margin /SYS/MB/VCORE_OBPS
- ERROR: Invalid processor speed. Failed to margin /SYS/MB/VNW_OBPS
ERROR: Invalid processor speed. Failed to margin /SYS/MB/VSB_OBPS
- PM
- ERROR: Speed mismatch detected.
- ERROR: Failed to margin /SYS/PM?/CMP?/VCORE_OBPS
- ERROR: Invalid processor speed. Failed to margin /SYS/PM?/CMP?/VNW_OBPS
ERROR: Invalid processor speed. Failed to margin /SYS/PM?/CMP?/VSB_OBPS

and hereby an example (output depends on the platform and system firmware):

- T3-1 (MB replacement)
-> start /SYS
     Are you sure you want to start /SYS (y/n)? y
     Starting /SYS
-> start /SP/console
     Are you sure you want to start /SP/console (y/n)? y
     [CPU 0:0:0] ERROR:   Invalid processor speed. Failed to margin /SYS/MB/VCORE_OBPS
     [CPU 0:0:0] ERROR:   Invalid processor speed. Failed to margin /SYS/MB/VNW_OBPS
     [CPU 0:0:0] ERROR:   Invalid processor speed. Failed to margin /SYS/MB/VSB_OBPS

- T4-4 (PM1 replacement)
-> start /SYS
     Are you sure you want to start /SYS (y/n)? y
     Starting /SYS
-> start /SP/console
     Are you sure you want to start /SP/console (y/n)? y
     ...
     [CPU 0:0:0] NOTICE: T4 Revision: 1.2
     [CPU 1:0:0] NOTICE: T4 Revision: 1.2
     [CPU 2:0:0] NOTICE: T4 Revision: 1.3
     [CPU 3:0:0] NOTICE: T4 Revision: 1.3
     ...
     [CPU 2:0:0] ERROR:   Speed mismatch detected. CMP Clock: 3000000 MHz CMP Rated: 2550000 MHz
     [CPU 3:0:0] ERROR:   Speed mismatch detected. CMP Clock: 3000000 MHz CMP Rated: 2550000 MHz
     ...
     [CPU 2:0:0] ERROR:   Failed to margin /SYS/PM1/CMP0/VCORE_OBPS
     [CPU 3:0:0] ERROR:   Failed to margin /SYS/PM1/CMP1/VCORE_OBPS
     ...
     [CPU 2:0:0] ERROR:   Invalid processor speed. Failed to margin /SYS/PM1/CMP0/VNW_OBPS
     [CPU 2:0:0] ERROR:   Invalid processor speed. Failed to margin /SYS/PM1/CMP0/VSB_OBPS
     [CPU 3:0:0] ERROR:   Invalid processor speed. Failed to margin /SYS/PM1/CMP1/VNW_OBPS
     [CPU 3:0:0] ERROR:   Invalid processor speed. Failed to margin /SYS/PM1/CMP1/VSB_OBPS

Cause

The reported failures are not caused by faulty/bad hardware, it has been caused by a bug in the system firmware (incorrect margining of the cpu voltage by hostconfig).

- Bug 15718010: SUNBT7048181 Invalid processor speed. Failed to margin errors on vnw and vsb with 3.0GHz T4 chips

and thereby it might be also caused by i2c issues (i2c_sp3: VNW_OBPS and VSB_OBPS converter), incorrect readings.

- Bug 15718010: SUNBT7048181 INVALID PROCESSOR SPEED. FAILED TO MARGIN ERRORS ON VNW AND VSB WIT
- Bug 15675385: SUNBT6992566 T3-1B: MCU ON SYSTEM 1035D400AM GOT DISABLED INTERMITTENTLY DURING

Solution

Advise is to perform the following actions:

- power-cycle system by disconnecting/connecting all ac power cables
- Performing an AC power cycle on the T3/T4/T5 Servers (Doc ID 1571054.1)
- if the failure still exists, upgrade system fw to 8.1.4.d or later (advise is to install latest system fw)
- SPARC T3/T4/T5 Series System Firmware and Patch Level Checklist (Doc ID 1400005.1)
- if the failure still exists, please open a service request by oracle support and collect an ilom snapshot (normal with fruid, log-ony mode: no)
- Collecting snapshot on ILOM 3.x and later platforms (Doc ID 1020204.1)
- Collecting snapshot via the GUI on ILOM 3.x and later platforms (Doc ID 1553399.1)
- Collect ILOM snapshot on T3-x and T4-x systems without an active network management connection (Doc ID 1518044.1)

Attachments

This solution has no attachment