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

Issue 737542 link

Starred by 2 users
Status: Verified
Owner:
█ roc...@chromium.org
please use my google.com address
Closed: Jun 2017
Cc:
saintlou@google.com
josa...@google.com
puneetster@google.com
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

Nothing displayed on screen instead of login screen.

Project Member Reported by hashimoto@chromium.org, Jun 28 2017 
Chrome Version: ToT
OS: Chrome OS

What steps will reproduce the problem?
(1) Boot Chromebook

What is the expected result?
Login screen is displayed.

What happens instead?
Screen totally black.
Nothing is displayed.

Please use labels and text to provide additional information.
Bisect says https://chromium-review.googlesource.com/c/546957/ is the first bad commit.

Comment 1 by hashimoto@chromium.org, Jun 28 2017 

In chrome log (/var/log/ui/ui.LATEST), the following lines repeatedly appear:

[2349:2410:0628/043809.076349:ERROR:validation_errors.cc(76)] Invalid message: VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0)
[2349:2410:0628/043809.076464:ERROR:browser_child_process_host_impl.cc(588)] Terminating child process for bad Mojo message: Received bad user message: Validation failed for GpuService ResponseValidator [VALIDATION_ERROR_UNEXPECTED_INVALID_HANDLE (invalid handle or interface ID in array expecting valid handles or interface IDs: array size - 1; index - 0)]
SYS_ioctl: VIDIOC_ENUM_FMT(2): fd=32, ret=-1, errno=22
SYS_ioctl: VIDIOC_ENUM_FMT(2): fd=32, ret=-1, errno=22

Comment 2 by roc...@chromium.org, Jun 28 2017 

Thanks for the logs. Reverting.

Comment 3 by hashimoto@chromium.org, Jun 28 2017 

Thank you for quickly handling the issue!

FWIW this issue has been observed on the following devices so far: kevin, lulu, kefka
(Please refer https://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices for device info)
Probably you can use any Chrome OS device to debug this issue.

Comment 4 by roc...@chromium.org, Jun 28 2017

Status: Fixed (was: Assigned)
Reverted in r482948

Comment 5 by helenzhang@chromium.org, Jul 13 2017

Status: Verified (was: Fixed)
Verified in Chrome OS 9740.0.0, 61.0.3155.0.
►

Sign in to add a comment