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

Issue 722616 link

Starred by 1 user
Status: Verified
Owner:
█ rahulchaudhry@chromium.org
Last visit > 30 days ago
Closed: Jun 2017
Cc:
█ shenhan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 711461



Sign in to add a comment

binutils-2.27: panther fails to boot

Project Member Reported by rahulchaudhry@chromium.org, May 15 2017 
Emerged binutils-2.27 in the chroot (cross-i686-pc-linux-gnu/binutils and cross-x86_64-cros-linux-gnu/binutils) configured with "--enable-compressed-debug-sections=none" (see https://bugs.chromium.org/p/chromium/issues/detail?id=715779).
Built panther image. Build was successful.

Flashed the image on a panther device using "cros flash ${IP} ${image}".
Cros flash reported that the device failed to come back online after reboot.

The device is unresponsive. It is not responding to pings. I cannot ssh into it. The display is blank.

Comment 1 by rahulchaudhry@chromium.org, May 23 2017 

I have verified that after forward-porting https://chromium-review.googlesource.com/#/c/278200 to binutils 2.27, panther boots fine.

This reverts upstream patch https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=d2667025dd30611514810c28bee9709e4623012a (from 15 Jun 2012).

We seem to have been carrying this local revert since at least the days of binutils 2.24.
I don't know what this does, and why we need to revert it to have a successful kernel boot.
Presumably, newer kernels build fine with newer binutils. Panther is still on kernel 3.8.11.
Maybe this needs to be fixed properly in upstream binutils, or maybe we need to back-port some kernel patches to our 3.8.11 tree.

Also, after simply forward-porting https://chromium-review.googlesource.com/#/c/278200 to binutils 2.27, a bunch of linker unittests start failing.

Comment 2 by llozano@chromium.org, May 23 2017

Cc: shenhan@chromium.org
added Han.

Han, do you remember anything about this?

Comment 3 by rahulchaudhry@chromium.org, Jun 1 2017

Status: Fixed (was: Assigned)
Fixed with https://android-review.googlesource.com/#/c/406077

Comment 4 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 5 by abod...@chromium.org, Aug 3 2017

Status: Verified (was: Fixed)
Closing. Please reopen it if its not fixed. Thanks!
►

Sign in to add a comment