Most of the FAFT tests failed when ran bios and ec suites with different RO and RW firmwares. |
|||
Issue description
Moblab 4: 8872.73.0
What steps will reproduce the problem?
(1) Crated a tunnel to access moblab 3
ssh -M -S /usr/local/google/home/venkataraju/.ssh/connections/moblab-sock-9083-80 -fNT -o ExitOnForwardFailure=yes -L 9083:localhost:80 moblab@100.107.195.209
2) created EC and BIOS suites selecting diffrerent RO and RW fimrares.
RO firmware: cave-firmware/R49-7820.197.0
RW firmware: cave-firmware/R49-7820.242.0
What is the expected result?
All tests should PASS
What happens instead?
- Most of the tests are FAILED.
- we also observed this kind of failures few days back for Terra 11 with different firmware combinations.
To see more logs: http://localhost:9084/afe/#tab_id=view_job&object_id=1574
Note: to accees moblab, make sure to create ssh tunnel (Please see at step 1 to create ssh tunnel)
Latest suite test result for Moblab: 100.107.195.217
Suite location: /mnt/moblab/results/1574-moblab/hostless
Test suite: cave-release/R56-9000.58.0-test_suites/control.faft_bios
1575-moblab 965 FAIL platform_ServoPowerStateController
1576-moblab 89 ERROR firmware_FwScreenCloseLid.dev
1577-moblab 94 ERROR firmware_FwScreenPressPower.dev
1578-moblab 94 ERROR firmware_UpdateFirmwareDataKeyVersion
1579-moblab 226 ERROR firmware_CorruptBothFwSigAB.dev
1580-moblab 333 GOOD firmware_UpdateKernelVersion.dev
1581-moblab 217 GOOD firmware_RONormalBoot.dev
1582-moblab 72 ERROR firmware_TPMExtend
1583-moblab 136 FAIL firmware_FAFTSetup
1584-moblab 270 GOOD firmware_CorruptFwSigB.normal
1585-moblab 38 GOOD firmware_Mosys.normal
1586-moblab 370 GOOD firmware_FWtries.dev
1587-moblab 301 GOOD firmware_CorruptKernelA.dev
1588-moblab 186 GOOD firmware_CorruptKernelA.normal
1589-moblab 437 GOOD firmware_EventLog
1590-moblab 213 ERROR firmware_RecoveryButton.dev
1591-moblab 268 GOOD firmware_TryFwB.dev
1592-moblab 288 ERROR firmware_CorruptBothFwBodyAB.dev
1593-moblab 72 ERROR firmware_RecoveryButton.normal
1594-moblab 248 ERROR firmware_TPMKernelVersion
1595-moblab 217 ERROR firmware_CorruptBothKernelAB.dev
1596-moblab 84 ERROR firmware_CorruptBothFwSigAB.normal
1597-moblab 82 ERROR firmware_CorruptBothFwBodyAB.normal
1598-moblab 215 ERROR firmware_DevBootUSB.dev
1599-moblab 152 GOOD firmware_TryFwB.normal
1600-moblab 147 ERROR firmware_RollbackFirmware.normal
1601-moblab 73 ERROR firmware_LegacyRecovery.normal
1602-moblab 64 GOOD firmware_RONormalBoot.normal
1603-moblab 332 GOOD firmware_CorruptFwBodyA.dev
1604-moblab 339 GOOD firmware_FWtries.normal
1605-moblab 90 ERROR firmware_InvalidUSB.normal
1606-moblab 421 GOOD firmware_CorruptKernelB.dev
1607-moblab 220 ERROR firmware_RollbackKernel.dev
1608-moblab 76 ERROR firmware_RollbackKernel.normal
1609-moblab 212 ERROR firmware_UserRequestRecovery.dev
1610-moblab 280 GOOD firmware_DevScreenTimeout.dev
1611-moblab 370 GOOD firmware_CorruptFwBodyB.dev
1612-moblab 53 GOOD firmware_TPMVersionCheck.normal
1613-moblab 206 GOOD firmware_CorruptFwBodyA.normal
1614-moblab 441 GOOD firmware_CorruptKernelB.normal
1615-moblab 195 GOOD firmware_TPMVersionCheck.dev
1616-moblab 225 ERROR firmware_RollbackFirmware.dev
1617-moblab 369 GOOD firmware_CorruptFwSigB.dev
1618-moblab 151 ERROR firmware_SelfSignedBoot.dev
1619-moblab 171 GOOD firmware_UpdateKernelDataKeyVersion.dev
1620-moblab 219 ERROR firmware_CorruptBothKernelAB.normal
1621-moblab 218 GOOD firmware_CorruptFwSigA.dev
1622-moblab 254 ERROR firmware_UserRequestRecovery.normal
1623-moblab 90 ERROR firmware_UpdateFirmwareVersion
1624-moblab 336 GOOD firmware_DevMode.normal
1625-moblab 212 GOOD firmware_UpdateKernelSubkeyVersion.dev
1626-moblab 484 GOOD firmware_CorruptFwSigA.normal
1627-moblab 121 GOOD firmware_FMap.normal
1628-moblab 449 GOOD firmware_CorruptFwBodyB.normal
Suite Duration: 12485 seconds or 3.47 hours
,
Mar 6 2017
We still have the issue? In issue 687674, it is said we have problem to flash firmware. There is possibly a problem with specific DUT (terra) you are using. There is a separate bug to track this https://b.corp.google.com/issues/35648324
,
Mar 6 2017
Reassign owner to update info.
,
Mar 13 2017
not seen this issue with recently tested firmware's. So closing. will reopen if we see it again. |
|||
►
Sign in to add a comment |
|||
Comment 1 by dchan@google.com
, Jan 13 2017