eRepair: Fix to handle incoming bad lanes threshold condition correctly

Change-Id: I5ef7429117f44fdadcf6844f4b2035b285910d1e
CQ:SW443542
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/65304
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com>
Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com>
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/65311
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>

src/import/chips/p9/procedures/hwp/io/p9_io_erepairAccessorHwpFuncs.H

@@ -945,7 +945,6 @@ fapi2::ReturnCode erepairSetFailedLanes(
         o_thresholdExceed = true;
     }
 
-fapi_try_exit:
     /*** Update the VPD ***/
 
     // Lets write the VPD of endpoint1 with faillanes on Rx side
@@ -966,6 +965,7 @@ fapi_try_exit:
               "tx l_setLanes() from Accessor HWP failed w/rc=0x%x",
               (uint64_t)fapi2::current_err );
 
+fapi_try_exit:
     FAPI_INF("<< erepairSetFailedLanes");
     return fapi2::current_err;
 }