New issue
Advanced search Search tips

Issue 778333 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

coreboot: reboot stalls on bob with cros_workon image

Project Member Reported by mka@chromium.org, Oct 25 2017

Issue description

I built an AP firmware image for bob from the firmware-gru-8785.B branch. The image boots, however on reboot the system stalls without any output on the serial console.

This build was done with cros_workon for the coreboot repository. Initially my tree had a local change in coreboot, which I reverted after running into the stalled reboot, but the issue also occurs without the change. Interestingly an image built without cros_workon does not have the reboot issue. My expectation was that a cros_workon image with no local changes would be functionally equivalent to a non-cros_workon image.

Images from both builds are attached.


Steps taken:

repo init -u https://chrome-internal.googlesource.com/chromeos/manifest-internal.git --repo-url='https://chromium.googlesource.com/external/repo.git' -b firmware-gru-8785.B
repo sync

./setup_board --board=bob
cros_workon-bob start coreboot

cros_workon-bob list
  => sys-boot/coreboot

# in src/third_party/coreboot
git log --oneline
  => 8c4eeee UPSTREAM: cr50: process uninitialized values gracefully
  (coincides with the hash in the coreboot ebuild)

emerge-bob chromeos-ec depthcharge coreboot libpayload chromeos-bootimage

flash /build/bob/firmware/image.dev.bin


# no cros_workon

cros_workon-bob stop coreboot

emerge-bob chromeos-ec depthcharge coreboot libpayload chromeos-bootimage

flash /build/bob/firmware/image.dev.bin
 
image.dev.bin.ko
8.0 MB Download
image.dev.bin.ok
8.0 MB Download
I chatted with mka@ and he said that his repo init was not fully clean.  He's going to try a fully clean one and report back.

Comment 2 by mka@chromium.org, Oct 26 2017

Status: WontFix (was: Unconfirmed)
The problem is not reproducible with a completely new repository.

Mea culpa, I expected repo init + sync to be equivalent.

Sign in to add a comment