Issue 37726 in chromium-os: Lumpy firmware update fails on dev-channel

[chrom...@googlecode.com]

Status: Untriaged
Owner: arsc...@chromium.org
CC: jay...@chromium.org, dgarr...@chromium.org, wfric...@chromium.org
Labels: Type-Bug Pri-1 Area-Installer Sev-1 Mstone-25

New issue 37726 by jay...@chromium.org: Lumpy firmware update fails on
dev-channel
http://code.google.com/p/chromium-os/issues/detail?id=37726

Starting Lumpy firmware updater v3 (bootok)...
- Updater package: [Google_Lumpy.2.111.0 / 02WQA015]
- Current system: [RO:Google_Lumpy.2.111.0 [RO_NORMAL],
ACT:Google_Lumpy.2.111.0 / 02WQA015]
- Write protection: Hardware: ON, Software: Main=ON
* invoke: flashrom -p internal:bus=spi -i RW_SECTION_A:_dup2_temp_from -i
RW_SECTION_B:_dup2_temp_to -r _dup2_temp_image
Execution failed (1): flashrom -p internal:bus=spi -i
RW_SECTION_A:_dup2_temp_from -i RW_SECTION_B:_dup2_temp_to -r
_dup2_temp_image
Messages:
Reading flash... FAILED
flashrom v0.9.4 : 7f7c711 : Oct 15 2012 18:45:30 UTC on Linux 3.4.0
(x86_64), built with libpci 3.1.10, GCC 4.7.x-google 20120720 (prerelease),
little endian
Block protection could not be disabled!
timeout, ICH9_REG_SSFS=0xf80000c0
flash partial read failed.Partial read operation failed!
FAILED.ERROR: Execution FAILED.
ERROR: Execution failed: ./updater3.sh (error code = 1)

Full logs are attached. Found in crash reports for dev-channel on R25. More
details at
https://crash.corp.google.com/reportdetail?reportid=f97cdca800fbb413.


Attachments:
log-f97cdca800fbb413.log 48.8 KB

[chrom...@googlecode.com]

Updates:
Cc: hun...@chromium.org

Comment #1 on issue 37726 by dgarr...@chromium.org: Lumpy firmware update

fails on dev-channel
http://code.google.com/p/chromium-os/issues/detail?id=37726

(No comment was entered for this change.)

[chrom...@googlecode.com]

Updates:
Cc: yj...@chromium.org dhend...@chromium.org

Comment #2 on issue 37726 by hun...@chromium.org: Lumpy firmware update

fails on dev-channel
http://code.google.com/p/chromium-os/issues/detail?id=37726

flashrom error -
+yjlou/dhendrix

[chrom...@googlecode.com]

Comment #3 on issue 37726 by dhend...@chromium.org: Lumpy firmware update

fails on dev-channel
http://code.google.com/p/chromium-os/issues/detail?id=37726

Hmmm, that SSFS value doesn't make any sense. Is this reproducible? If
possible I'd like to get verbose output by adding -V to that command when
the failure happens and capture a log:

flashrom -p internal:bus=spi -i RW_SECTION_A:_dup2_temp_from -i

RW_SECTION_B:_dup2_temp_to -r _dup2_temp_image -V 2>&1 | tee
flashrom_fail.txt

[chrom...@googlecode.com]

Updates:
Status: Assigned
Owner: dhend...@chromium.org

Comment #5 on issue 37726 by arsc...@chromium.org: Lumpy firmware update

fails on dev-channel
http://code.google.com/p/chromium-os/issues/detail?id=37726

[chrom...@googlecode.com]

Comment #6 on issue 37726 by jay...@chromium.org: Lumpy firmware update

fails on dev-channel
http://code.google.com/p/chromium-os/issues/detail?id=37726

dhendrix: As mentioned, this is from a crash report. You might have to
reproduce it yourself as I don't know of a way to contact the owner of the
device.