flashupdate -c/-u doesn't operate correctly

BugID: 4638200

Symptom: Someone updating an SB from 5.12.5 to 5.12.6 using flashupdate -c/-u encounters the following error after doing setkey off/on. This issue is fixed in 5.13.0.

Feb 14 13:29:48 v4u-4800e Domain-A.SC: /N0/SB2: marked as Failed! errorReg = 0x00c1                  

and:

Feb 14 13:29:49 v4u-4800e Domain-A.SC: 
/partition0/domain0/SB2/ar0: 
    SafariPortError1[0x210] : 0x00010001
                 AdrPErr [00:00] : 0x1 Address parity error
              AccAdrPErr [16:16] : 0x1 accumulated address parity errors
    SafariPortError3[0x230] : 0x00010001
                 AdrPErr [00:00] : 0x1 Address parity error
              AccAdrPErr [16:16] : 0x1 accumulated address parity errors
>>> SafariPortError5[0x250] : 0x00018001
                 AdrPErr [00:00] : 0x1 Address parity error
                      FE [15:15] : 0x1 
              AccAdrPErr [16:16] : 0x1 accumulated address parity errors

{/N0/SB4/P0} Subtest: E-Cache Global Variables Initialization 
{/N0/SB4/P1} Subtest: Fast Init. Verification Test 
Feb 14 13:29:49 v4u-4800e Domain-A.SC: 
/partition0/domain0/SB2/bbcGroup0/sbbc0: 
>>> ErrorStatus[0x80] : 0x80008300
                      FE [15:15] : 0x1 
                  ErrSum [31:31] : 0x1 
                  SafErr [09:08] : 0x3 Fireplane device asserted an error

{/N0/SB4/P2} Subtest: E-Cache Global Variables Initialization 
{/N0/SB4/P0} Subtest: Fast Init. Verification Test 
{/N0/SB4/P2} Subtest: Fast Init. Verification Test 
{/N0/SB4/P3} Subtest: E-Cache Global Variables Initialization 
{/N0/SB4/P3} Subtest: Fast Init. Verification Test 
Feb 14 13:29:50 v4u-4800e Domain-A.SC: 
/partition0/domain0/SB2/bbcGroup0/cpuAB/cpusafariagent0: 
    AFAR (high)[0x531] : 0x00000600
            AFAR [42:32] [10:00] : 0x600 
    AFAR (low)[0x541] : 0x00400040
    AFAR_2 (high)[0x571] : 0x00000040
          AFAR_2 [42:32] [10:00] : 0x40 
    AFAR_2 (low)[0x581] : 0x00010000
    AFSR (high)[0x551] : 0x00381000
                    PERR [19:19] : 0x1 
                    PRIV [20:20] : 0x1 
                      ME [21:21] : 0x1 
                      TO [12:12] : 0x1 
    AFSR_2 (high)[0x591] : 0x00080000
                    PERR [19:19] : 0x1 
    EMU B[0x511] : 0x40000000
                 HBM_ERR [30:30] : 0x1 

Feb 14 13:29:50 v4u-4800e Domain-A.SC: 
/partition0/domain0/SB2/bbcGroup0/cpuAB/cpusafariagent1: 
    AFAR (high)[0x531] : 0x00000600
            AFAR [42:32] [10:00] : 0x600 
    AFAR (low)[0x541] : 0x00400040
    AFAR_2 (high)[0x571] : 0x000000ef
          AFAR_2 [42:32] [10:00] : 0xef 
>>> AFAR_2 (low)[0x581] : 0xbebafaa0
    AFSR (high)[0x551] : 0x00381000
                    PERR [19:19] : 0x1 
                    PRIV [20:20] : 0x1 
                      ME [21:21] : 0x1 
                      TO [12:12] : 0x1 
    AFSR_2 (high)[0x591] : 0x00080000
                    PERR [19:19] : 0x1 
    EMU B[0x511] : 0x40000000
                 HBM_ERR [30:30] : 0x1 

Feb 14 13:29:50 v4u-4800e Domain-A.SC: 
/partition0/domain0/SB2/bbcGroup1/sbbc1: 
>>> ErrorStatus[0x80] : 0x81008200
                      FE [15:15] : 0x1 
                  ErrSum [31:31] : 0x1 
                  SafErr [09:08] : 0x2 Fireplane device asserted an error
               AccSafErr [25:24] : 0x1 

Feb 14 13:29:50 v4u-4800e Domain-A.SC: 
/partition0/domain0/SB2/bbcGroup1/cpuCD/cpusafariagent1: 
    AFAR (high)[0x531] : 0x00000600
            AFAR [42:32] [10:00] : 0x600 
    AFAR (low)[0x541] : 0x00400040
    AFAR_2 (high)[0x571] : 0x00000004
          AFAR_2 [42:32] [10:00] : 0x4 
    AFAR_2 (low)[0x581] : 0x00000840
    AFSR (high)[0x551] : 0x00381000
                    PERR [19:19] : 0x1 
                    PRIV [20:20] : 0x1 
                      ME [21:21] : 0x1 
                      TO [12:12] : 0x1 
    AFSR_2 (high)[0x591] : 0x00080000
                    PERR [19:19] : 0x1 
    EMU B[0x511] : 0x40000000
                 HBM_ERR [30:30] : 0x1                   

Workaround:

Use flashupdate -f < URL > < affected-SB >. flashupdate -f from an external source reprograms the board correctly.

Power off the board, remove the board, and then reinsert and power it back on. Doing this resets the board programming which flashupdate -c/-u fails to do and the board will work fine again. Note that the board must be physically removed/reinserted. Doing a poweroff and poweron is NOT sufficient.

Notes:

This happens only if a board is inserted, powered on and POST'ed and then a flashupdate -c/-u is performed. If you flashupdate -c before the board is brought up, you don't run into this issue. Users forgetting to flashupdate first and then going back to update will encounter this issue.

This issue is fixed in 5.13.0.

Keywords: flashupdate, 5.12.5, 5.12.6

• Submitted by CPRE - Send questions to beverly.kobus@sun.com