[platform_Flashrom] Execution failed (1): flashrom -p host --fast-verify -w bios.bin...Erasing and writing flash chip... FAILED |
||||
Issue descriptionFirst time platform_Flashrom failed with this reason was on R69-10741.0.0 with hana device on R69-10741.0.0 as a single flake, but coming back more often and now is consistent on 3 boards: - cyan, - rikku - samus, Test results screenshot: https://screenshot.googleplex.com/CmrC0oCePyG Failure reason: Expect (factory_install) completed. in output of Starting Google_Cyan firmware updater v4 (factory_install)... Sample logs at https://storage.cloud.google.com/chromeos-autotest-results/220297603-chromeos-test/chromeos15-row13b-rack1-host3/debug/autoserv.DEBUG test log showing the issue: () 07/24 19:25:39.989 INFO | platform_Flashrom:0039| Execute flashrom -p host --wp-status 2>&1 07/24 19:25:40.641 INFO | platform_Flashrom:0041| Output >>> ['flashrom v0.9.9 : 622128c : Jul 05 2018 14:19:12 UTC on Linux 3.18.0-18113-ge3cdebd416dd (x86_64)', 'coreboot table found at 0x7cc22000.', 'Mapping BYT IBASE at 0xfed08000, unaligned size 0x200.', 'Mapping BYT SBASE at 0xfed01000, unaligned size 0x200.', 'WP: status: 0x0000', 'WP: status.srp0: 0', 'WP: status.srp1: 0', 'WP: write protect is disabled.', 'WP: write protect range: start=0x00000000, len=0x00000000'] <<< 07/24 19:25:40.642 INFO | platform_Flashrom:0039| Execute flashrom -p ec --wp-status 2>&1 07/24 19:25:41.052 INFO | platform_Flashrom:0041| Output >>> ['flashrom v0.9.9 : 622128c : Jul 05 2018 14:19:12 UTC on Linux 3.18.0-18113-ge3cdebd416dd (x86_64)', 'coreboot table found at 0x7cc22000.', 'Mapping BYT IBASE at 0xfed08000, unaligned size 0x200.', 'Mapping BYT SBASE at 0xfed01000, unaligned size 0x200.', 'WP: status: 0x00', 'WP: status.srp0: 0', 'WP: write protect is disabled.', 'WP: write protect range: start=0x00000000, len=0x00000000'] <<< 07/24 19:25:41.053 INFO | platform_Flashrom:0039| Execute flashrom -E -i RW_SECTION_B 2>&1 07/24 19:25:48.783 INFO | platform_Flashrom:0041| Output >>> ['flashrom v0.9.9 : 622128c : Jul 05 2018 14:19:12 UTC on Linux 3.18.0-18113-ge3cdebd416dd (x86_64)', 'Calibrating delay loop... OK.', 'coreboot table found at 0x7cc22000.', 'Mapping BYT IBASE at 0xfed08000, unaligned size 0x200.', 'Mapping BYT SBASE at 0xfed01000, unaligned size 0x200.', 'Erasing and writing flash chip... SUCCESS'] <<< 07/24 19:25:48.783 INFO | platform_Flashrom:0039| Execute chromeos-firmwareupdate --mode=factory 2>&1 07/24 19:26:15.267 INFO | platform_Flashrom:0041| Output >>> ['Starting Google_Cyan firmware updater v4 (factory_install)...', ' - Updater package: [RO:Google_Cyan.7287.57.100 RW:Google_Cyan.7287.57.180 / EC:cyan_v1.1.3571-7ae3bf3]', ' - Current system: [RO:Google_Cyan.7287.57.100 , ACT:Google_Cyan.7287.57.180 / EC:cyan_v1.1.3575-c3321a1]', ' - Write protection: Hardware: off, Software: Main=off EC=off', ' * invoke: flashrom -p host --fast-verify -w bios.bin', ' * invoke: flashrom -p ec --fast-verify -w ec.bin', ' Execution failed (1): flashrom -p ec --fast-verify -w ec.bin', ' Messages:', 'Calibrating delay loop... OK.', 'coreboot table found at 0x7cc22000.', 'flashrom v0.9.9 : 622128c : Jul 05 2018 14:19:12 UTC on Linux 3.18.0-18113-ge3cdebd416dd (x86_64)', 'Mapping BYT IBASE at 0xfed08000, unaligned size 0x200.', 'Mapping BYT SBASE at 0xfed01000, unaligned size 0x200.', 'No erasers found for this chip (smsc:mec1322)!', 'ERROR: Execution FAILED.', 'ERROR: Execution failed: ./updater4.sh (error code = 1)'] <<< 07/24 19:26:15.268 DEBUG| test:0410| Test failed due to Expect (factory_install) completed. in output of Starting Google_Cyan firmware updater v4 (factory_install)... - Updater package: [RO:Google_Cyan.7287.57.100 RW:Google_Cyan.7287.57.180 / EC:cyan_v1.1.3571-7ae3bf3] - Current system: [RO:Google_Cyan.7287.57.100 , ACT:Google_Cyan.7287.57.180 / EC:cyan_v1.1.3575-c3321a1] - Write protection: Hardware: off, Software: Main=off EC=off * invoke: flashrom -p host --fast-verify -w bios.bin * invoke: flashrom -p ec --fast-verify -w ec.bin Execution failed (1): flashrom -p ec --fast-verify -w ec.bin Messages: Calibrating delay loop... OK. coreboot table found at 0x7cc22000. flashrom v0.9.9 : 622128c : Jul 05 2018 14:19:12 UTC on Linux 3.18.0-18113-ge3cdebd416dd (x86_64) Mapping BYT IBASE at 0xfed08000, unaligned size 0x200. Mapping BYT SBASE at 0xfed01000, unaligned size 0x200. No erasers found for this chip (smsc:mec1322)! ERROR: Execution FAILED. ERROR: Execution failed: ./updater4.sh (error code = 1). Exception log follows the after_iteration_hooks. 07/24 19:26:15.268 DEBUG| test:0415| Starting after_iteration_hooks for platform_Flashrom
,
Jul 25
,
Jul 25
for why M70 runs are not getting scheduled see crbug.com/866768 from b/111654268 I'd suspect builds with https://chromium-review.googlesource.com/c/chromiumos/third_party/flashrom/+/1139405 will be in a good state for this test it looks like that change landed after M70 branch, so I think it will need to be merged to M69
,
Jul 25
yes, M69 cherry-pick is on its way
,
Jul 25
Thanks kmshelton@ and vbendeb@ for the update. I'll continue monitoring the test, and look forward to the fix.
,
Jul 26
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ka...@chromium.org
, Jul 25