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

Issue 831626 link

Starred by 1 user
Status: Fixed
Owner:
sky@chromium.org
Closed: Apr 2018
Cc:
█ dianwa@chromium.org
█ jlklein@chromium.org
█ pbe...@chromium.org
pmarko@chromium.org
alemate@chromium.org
khorimoto@chromium.org
█ marc...@chromium.org
█ jhawkins@chromium.org
sheckylin@chromium.org
mustash-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

veyron_minnie can't boot on HEAD

Project Member Reported by hansberry@chromium.org, Apr 11 2018 
Chrome Version: HEAD
OS: R67-10560.0.0

Minnie builds fine on head, but when I deploy it to my Minnie, it freezes on the Chrome OS boot screen. When I inspect /var/log/ui/ui.LATEST, I see:

[6055:6055:0411/084713.019984:FATAL:window_tree_host_manager.cc(234)] Check failed: display::kInvalidDisplayId != primary_display_id (-1 vs. -1)
#0 0x000005ad8f54 <unknown>
etc...

If I comment out this check and try re-deploying, the Minnie segfaults:

Received signal 11 SEGV_MAPERR 0000000000f0
#0 0x0000024dbf54 
#1 0x0000024dbed4 <unknown>

Comment 1 by khorimoto@chromium.org, Apr 11 2018

Cc: alemate@chromium.org pbe...@chromium.org sheckylin@chromium.org dianwa@chromium.org
CC'ing sheriffs/gardener

Comment 2 by alemate@chromium.org, Apr 11 2018

Cc: marc...@chromium.org

Comment 3 by pmarko@chromium.org, Apr 12 2018

Cc: pmarko@chromium.org
In case it helps investigating: I've got the same error on betty VM after deploying ToT chrome.

Comment 4 by marc...@chromium.org, Apr 16 2018

Status: Fixed (was: Assigned)
The fix for this has landed on ToT chrome.
►

Sign in to add a comment