SPARC T3-1 wont boot due to FATAL ERROR:" FATAL: millbrook_inband_read: Timed out waiting for config read to succeed to Node0.MCU1.BoB2.Dev0.Func1.Reg0xe9.[CPU 0:0:0] Fatal configuration error

Asset ID:	1-72-1512188.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 1512188.1 : SPARC T3-1 wont boot due to FATAL ERROR:" FATAL: millbrook_inband_read: Timed out waiting for config read to succeed to Node0.MCU1.BoB2.Dev0.Func1.Reg0xe9.[CPU 0:0:0] Fatal configuration error - forcing power-down"

Applies to:

SPARC T3-1 - Version Not Applicable to Not Applicable [Release N/A]
SPARC

Symptoms

SPARC T3-1 not bootable due to Fatal error when testing memory link during POST.

"Fatal configuration error - forcing power-down" during initialization of the SMI channels during POST:

.
[CPU 0:0:0] NOTICE: Initializing MCU 0
[CPU 0:0:0] NOTICE: Initializing MCU 1
[CPU 0:0:0] NOTICE: SMI Channel 0, SB Mapping 0 -- ERRCNT:     0x0     LNERR: 0x0
[CPU 0:0:0] NOTICE: SMI Channel 0, SB Mapping 1 -- ERRCNT:     0x0     LNERR: 0x0
[CPU 0:0:0] NOTICE: SMI Channel 1, SB Mapping 0 -- ERRCNT:     0x0     LNERR: 0x0
[CPU 0:0:0] NOTICE: SMI Channel 1, SB Mapping 1 -- ERRCNT:     0x0     LNERR: 0x0
[CPU 0:0:0] NOTICE: SMI Channel 0, SB Mapping 0 -- ERRCNT:     0x0     LNERR: 0x0
[CPU 0:0:0] NOTICE: SMI Channel 0, SB Mapping 1 -- ERRCNT:     0x0     LNERR: 0x0
[CPU 0:0:0] NOTICE: SMI Channel 1, SB Mapping 0 -- ERRCNT:     0x0     LNERR: 0x0
[CPU 0:0:0] NOTICE: SMI Channel 1, SB Mapping 1 -- ERRCNT:     0x0     LNERR: 0x0
[CPU 0:0:0] FATAL:   millbrook_inband_read: Timed out waiting for config read to succeed to Node0.MCU1.BoB2.Dev0.Func1.Reg0xe9.[CPU 0:0:0] Fatal configuration error - forcing power-down

Cause

Memory test routine may fail sometimes during POST which will prevent the system from booting.

Solution

SunPatch:145665-03; FW 8.0.4.c (or later)

References

<BUG:15662119> - SUNBT6970989-1.0.0 IBIST FIXUP, AND LOWER CONFIG ACCESS LIMIT DURING CHECK_SMI_L
<BUG:15657502> - SUNBT6970989-1.0.X IBIST FIXUP, AND LOWER CONFIG ACCESS LIMIT DURING CHECK_SMI_L

Attachments

This solution has no attachment