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

Issue 772450 link

Starred by 1 user

Issue metadata

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

Blocked on:
issue 765844



Sign in to add a comment

daisy canaries failing in Archive step (kernel > 8MB)

Project Member Reported by manojgupta@chromium.org, Oct 6 2017

Issue description

Daisy builds are failing in archive stage since the kernel image > 8 MB.

https://uberchromegw.corp.google.com/i/chromeos/builders/daisy-release/builds/1558

 FDT:          fdt@17
 * Kernel image size is 8389488 bytes.
 * ERROR: sys-kernel/chromeos-kernel-3_8-3.8.11-r635::chromiumos failed (install phase):
 *   Kernel image is larger than 8 MB.
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_install
 *   environment, line 5127:  Called cros-kernel2_src_install
 *   environment, line 1690:  Called die
 * The specific snippet of code:
 *               die "Kernel image is larger than ${kern_max} MB.";
 * 
 * If you need support, post the output of `emerge --info '=sys-kernel/chromeos-kernel-3_8-3.8.11-r635::chromiumos'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/chromeos-kernel-3_8-3.8.11-r635::chromiumos'`.
 * The complete build log is located at '/build/daisy/tmp/portage/logs/sys-kernel:chromeos-kernel-3_8-3.8.11-r635:20171006-115422.log'.
 * For convenience, a symlink to the build log is located at '/build/daisy/tmp/portage/sys-kernel/chromeos-kernel-3_8-3.8.11-r635/temp/build.log'.
 * The ebuild environment file is located at '/build/daisy/tmp/portage/sys-kernel/chromeos-kernel-3_8-3.8.11-r635/temp/environment'.
 * Working directory: '/mnt/host/source/src/third_party/kernel/v3.8'
 * S: '/mnt/host/source/src/third_party/kernel/v3.8'

>>> Failed to emerge sys-kernel/chromeos-kernel-3_8-3.8.11-r635 for /build/daisy/, Log file:

 
Cc: dgarr...@chromium.org pho...@chromium.org
CCing Infra deputies.
Owner: laszio@chromium.org
Status: Started (was: Untriaged)
This is probably due to enabling afdo on kernel, although we had been doing so for past few months and just disabled it two weeks ago and reenable it this week. I'll take this.
Cc: diand...@chromium.org
The size overflow problem only happens when building recovery image. I'm trying to see if it is possible to enable the afdo for non-recovery image.
dianders@ has a CL under review, which can save more than 700KB on recover image. We are only 880 bytes off so that seems the way to go.

Backup solutions:
1. disable autofdo on recover image.
2. disable autofdo on daisy.
I get a "404 not found" when I follow that link.. (temporary issue?)
the link is fine and works fine from here but from within gmail the links includes the ">" character at the end. 
Blockedon: 765844
Blocking bug is fixed.  ...so presumably this is fixed too.
Owner: diand...@chromium.org
Status: Fixed (was: Started)
Status: Available (was: Fixed)
Doh.  Apparently another change landed at nearly the same time that made the futility change not help.  So reverting it...  We need to find more space somewhere else I guess.
Cc: vapier@chromium.org
Owner: manojgupta@chromium.org
Status: Started (was: Available)
https://chromium-review.googlesource.com/c/chromiumos/platform/crosutils/+/716922
Project Member

Comment 14 by bugdroid1@chromium.org, Oct 13 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/crosutils/+/ea180c04ac4e9c11d4a59e33e0ddb3691ca71b04

commit ea180c04ac4e9c11d4a59e33e0ddb3691ca71b04
Author: Manoj Gupta <manojgupta@google.com>
Date: Fri Oct 13 09:29:15 2017

recovery: Disable kernel_afdo on recovery image.

kernel afdo was enabled on recovery images but it pushed the
image to > 8MB on daisy boards resulting in failure at Archive stage.
Since there is no need that recovery image kernel for afdo, just disable it.

BUG= chromium:772450 
TEST=Recovery image size is < 8MB on daisy.

Change-Id: I8e12279ccfc53a4598cbd45710abd5c0db014f50
Reviewed-on: https://chromium-review.googlesource.com/716922
Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Trybot-Ready: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Ting-Yuan Huang <laszio@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/ea180c04ac4e9c11d4a59e33e0ddb3691ca71b04/mod_image_for_recovery.sh

Status: Verified (was: Started)
Last daisy canary build passed the recovery image stage so closing this.
https://uberchromegw.corp.google.com/i/chromeos/builders/daisy-release/builds/1579

Sign in to add a comment