New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 680647 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Jan 2018
Cc:
█ andycai@chromium.org
█ lhui@chromium.org
█ twreid@chromium.org
dchan@chromium.org
█ krk@chromium.org
█ tgillella@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

provision_FirmwareUpdate failed with "ERROR: No GBB found in /tmp/gbb"

Project Member Reported by venkatar...@chromium.org, Jan 12 2017 
Moblab Version: R55-8872.67.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 using new user interface (moblab->run suite) without selecting RO and RW firmwares.
    (Ater step2, tests are running successfully)

(3) few hours later created EC and BIOS suites using old interface by selecting 
     RO firmware: cave-firmware/R49-7820.197.0
     RW firmware: cave-firmware/R49-7820.242.0

What is the expected result?
   - New suites (which are created at step 3) should run after completion of the old suites(which are created at step 2)

What happens instead?
   - New suite tests failed with "ERROR: No GBB found in /tmp/gbb" during provision_FirmwareUpdate


01/11 22:28:48.066 INFO |             servo:0649| Will execute on servo host: cp /tmp/_autotmp_NZNPslfwimage/image.bin /tmp/fw_main
01/11 22:28:48.066 DEBUG|        base_utils:0185| Running 'sudo -n sh -c "cp /tmp/_autotmp_NZNPslfwimage/image.bin /tmp/fw_main"'
01/11 22:28:48.091 DEBUG|        base_utils:0185| Running 'sudo -n sh -c "stat -c '%s' /tmp/fw_main"'
01/11 22:28:48.100 DEBUG|        base_utils:0280| [stdout] 16777216
01/11 22:28:48.101 INFO |             servo:0649| Will execute on servo host: flashrom -p dummy:image=/tmp/fw_main,size=16777216,emulate=VARIABLE_SIZE -w /tmp/fw_main -i RO_VPD:/tmp/ro_vpd -i RW_VPD:/tmp/rw_vpd
01/11 22:28:48.102 DEBUG|        base_utils:0185| Running 'sudo -n sh -c "flashrom -p dummy:image=/tmp/fw_main,size=16777216,emulate=VARIABLE_SIZE -w /tmp/fw_main -i RO_VPD:/tmp/ro_vpd -i RW_VPD:/tmp/rw_vpd"'
01/11 22:28:48.111 ERROR|        base_utils:0280| [stderr] flashrom v0.9.4  : 1649d16 : Oct 01 2016 07:03:05 UTC on Linux 3.14.0 (x86_64)
01/11 22:28:48.112 ERROR|        base_utils:0280| [stderr] flashrom v0.9.4  : 1649d16 : Oct 01 2016 07:03:05 UTC on Linux 3.14.0 (x86_64)
01/11 22:28:50.228 DEBUG|        base_utils:0280| [stdout] Erasing and writing flash chip... Verifying flash... VERIFIED.          
01/11 22:28:50.231 DEBUG|        base_utils:0280| [stdout] SUCCESS
01/11 22:28:50.244 DEBUG|        base_utils:0185| Running 'sudo -n sh -c "gbb_utility -g --hwid /tmp/gbb"'
01/11 22:28:50.259 ERROR|        base_utils:0280| [stderr] ERROR: No GBB found in /tmp/gbb
01/11 22:28:50.260 ERROR|        servo_host:0305| Command <sudo -n sh -c "gbb_utility -g --hwid /tmp/gbb"> failed, rc=1, Command returned non-zero exit status
* Command: 
    sudo -n sh -c "gbb_utility -g --hwid /tmp/gbb"
Exit status: 1
Duration: 0.011528968811

stderr:
ERROR: No GBB found in /tmp/gbb
01/11 22:28:50.261 INFO |             servo:0508| Setting power_state to reset

attaching generate logs
cave_dut_log-011217-103522.tar.gz
2.0 MB Download
1343-moblab.tar.bz2
2.7 MB Download

Comment 1 by ntang@google.com, Mar 6 2017 

From the the log, the command to generate the gbb file seems to succeeded:
flashrom -V -p ft2232_spi:type=servo-v2 -r -i GBB:/tmp/gbb /tmp/fw_main

But the command to read the gbb file failed:
gbb_utility -g --hwid /tmp/gbb

Your moblab IP address seems to have changed. Could you check if you still have the problem? If so, let me know so that I could take a look at.

Comment 2 by dtapu...@chromium.org, Nov 10 2017

Components: Infra>Client>ChromeOS

Comment 3 by haddowk@chromium.org, Jan 12 2018

Status: Archived (was: Untriaged)
►

Sign in to add a comment