Chrome Version: 61.0.3117.0
Chrome OS Version: R61-9609.0.0
Chrome OS Platform: samus
Network info: Corp Ethernet

Steps To Reproduce:
(1) Follow steps in simple chrome workflow (https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md) on a samus device.

Expected Result:
When deploy_chrome says "Starting UI...", the UI starts again.

Actual Result:
The screen stays dark. It is still possible to ssh in and logs show errors:

/var/log/ui/ui.LATEST:

[21613:21619:0718/164619.203632:ERROR:drm_device.cc(414)] Drm atomic requested but capabilities don't allow it. To switch to legacy page fli
p remove the command line flag enable-drm-atomic
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
Received signal 11 SEGV_MAPERR 000000000058
#0 0x5957704bdeec <unknown>
#1 0x5957704bda41 <unknown>
#2 0x7d6f8b1cc580 <unknown>
#3 0x59576e9b7ee9 <unknown>
#4 0x59576e9ad593 <unknown>
#5 0x59576e9c3c2f <unknown>
#6 0x59577055266a <unknown>
#7 0x5957704d93ff <unknown>
#8 0x5957704d97fb <unknown>
#9 0x5957704d9c54 <unknown>
#10 0x5957704db3e9 <unknown>
#11 0x5957704fc8b6 <unknown>
#12 0x595770523648 <unknown>
#13 0x59577051e37d <unknown>
#14 0x7d6f8b1c2558 <unknown>
#15 0x7d6f89ef908d clone
  r8: 0000000000000000  r9: 000000000000000b r10: 0000000000000001 r11: 000059576e9ad430
 r12: 0000000000000005 r13: 0000000034325258 r14: 000059577691c750 r15: 0000000000000000
  di: 0000000000000000  si: 00007d6f869508f8  bp: 00007d6f869508a0  bx: 000030964016d700
  dx: 000030963ffec408  ax: 0000000000000000  cx: 2cb0126632b26c00  sp: 00007d6f869507e0
  ip: 000059576e9b7ee9 efl: 0000000000010246 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000058
[end of stack trace]
Calling _exit(1). Core file will not be generated.

/var/log/chrome/chrome:

[3437:3502:0718/165028.412733:VERBOSE1:drm_device_handle.cc(83)] Succeeded authenticating /dev/dri/card0 in 0 ms with 1 attempt(s)
[22566:22572:0718/165028.447162:ERROR:drm_device.cc(414)] Drm atomic requested but capabilities don't allow it. To switch to legacy page flip remove the command line flag enable-drm-atomic
[22566:22572:0718/165028.447227:VERBOSE1:drm_device_manager.cc(54)] Could not initialize DRM device for /sys/devices/pci0000:00/0000:00:02.0/drm/card0

/var/log/messages:

2017-07-18T16:51:16.828788-07:00 WARNING session_manager[3422]: [WARNING:liveness_checker_impl.cc(68)] Browser hang detected!
2017-07-18T16:51:41.829566-07:00 ERR session_manager[3422]: [ERROR:object_proxy.cc(582)] Failed to call method: org.chromium.LibCrosServiceInterface.CheckLiveness: object_path= /org/chromium/LibCrosService: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

When restarting it hangs on the Chrome logo screen.

How frequently does this problem reproduce? Always

What is the impact to the user, and is there a workaround? If so, what is it?
Chrome developers aren't able to test changes on ChromeOS.