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" (Doc ID 1512188.1)

Last updated on JULY 01, 2016

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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms