Chromium build for guado broken at head/lkgr

16 views
Skip to first unread message

Luke Sorenson

unread,
Mar 15, 2018, 12:21:14 PM3/15/18
to chromiu...@chromium.org, Simon Que, Daniel Fenner
To whom it may concern,

I am working on fixing an unrelated bug on Chromium / Chrome OS on guado devices, but I am blocked because Chromium appears to be broken for this device.

I am building a fresh checkout of Chrome OS for guado and flashing the device with a USB stick. This works fine. The Chromium build that comes with Chrome OS functions correctly.

When I attempt to deploy_chrome with a Default build of a fresh checkout of either master or lkgr, the device is in a broken state, where both connected displays are black.

In /var/log/ui/ui.LATEST, I can see the following error:
[10961:10965:0315/091142.674164:ERROR:hardware_display_plane_manager.cc(274)] Failed to find a free plane for crtc 20
[10961:10965:0315/091142.674367:ERROR:crtc_controller.cc(103)] Failed to assign overlay planes for crtc 20: No such device (19)
[10961:10961:0315/091142.675629:ERROR:gles2_cmd_decoder.cc(16138)] Context lost because SwapBuffers failed.
[10961:10965:0315/091142.674747:FATAL:drm_thread.cc(217)] Check failed: result. DrmThread::SchedulePageFlip failed.

To get around this for now, I will probably try to build an older version of Chromium for guado. But this is probably something that should be looked at?

Thanks in advance,

Luke

--

Luke Sorenson |
 Software Engineer | (646) 300-4506 | las...@google.com

Vincent Palatin

unread,
Mar 15, 2018, 12:38:56 PM3/15/18
to Luke Sorenson, Chromium OS dev, Simon Que, Daniel Fenner, Greg Levin
On Thu, Mar 15, 2018 at 5:20 PM, 'Luke Sorenson' via Chromium OS dev <chromiu...@chromium.org> wrote:
To whom it may concern,

I am working on fixing an unrelated bug on Chromium / Chrome OS on guado devices, but I am blocked because Chromium appears to be broken for this device.

I am building a fresh checkout of Chrome OS for guado and flashing the device with a USB stick. This works fine. The Chromium build that comes with Chrome OS functions correctly.

When I attempt to deploy_chrome with a Default build of a fresh checkout of either master or lkgr, the device is in a broken state, where both connected displays are black.

In /var/log/ui/ui.LATEST, I can see the following error:
[10961:10965:0315/091142.674164:ERROR:hardware_display_plane_manager.cc(274)] Failed to find a free plane for crtc 20
[10961:10965:0315/091142.674367:ERROR:crtc_controller.cc(103)] Failed to assign overlay planes for crtc 20: No such device (19)
[10961:10961:0315/091142.675629:ERROR:gles2_cmd_decoder.cc(16138)] Context lost because SwapBuffers failed.
[10961:10965:0315/091142.674747:FATAL:drm_thread.cc(217)] Check failed: result. DrmThread::SchedulePageFlip failed.

To get around this for now, I will probably try to build an older version of Chromium for guado.


Indeed, you can always sync to the tag of last version of Chrome will successfully passed the PFQ, normally the Chrome PFQ more or less guarantee that you avoid this kind of total breakage,
right now it is still : 67.0.3369

 
But this is probably something that should be looked at?

AFAIU that's part of the job of the Chrome gardener 
CC'ing him


Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages