I saw three boots in kernel log. The first one, kernel crashed soon after cryptohome is created (probably is the first kiosk run). From 2nd one on, the SDD seems becoming bad: 

e.g.
2016-05-06T13:46:53.777308-07:00 ERR kernel: [   52.554973] blk_update_request: I/O error, dev mmcblk0rpmb, sector 0

And I saw problem with frecon, which might be the cause of VT2 switching problem:

2016-05-06T13:47:50.872942-07:00 WARNING kernel: [  109.648289] frecon(506): Unable to set crtc: Invalid argument

I suspect the later is caused by the faulty SSD. Do you have another cyan device to try?

give me a few minutes. Thanks for looking into it

behaviour observed in a different cyan running the same image:
CHROMEOS_RELEASE_DESCRIPTION=8283.0.0 (Official Build) dev-channel cyan test

Deleted: log-050616-165200.tar.gz 531 KB

log-050616-165200.tar.gz 531 KB Download

Sounds serious. Upping priority for M-52.

I suspect we are seeing something similar in  issue 588425 .

frecon crashed in the first boot (2016-05-06T23:47:41) and 2nd boot (2016-05-06T16:51:09):

2016-05-06T23:47:41.334812+00:00 INFO kernel: [    1.260470] frecon[110]: segfault at 10 ip 00007fbcf349d5d8 sp 00007ffd18260290 error 4 in frecon[7fbcf3498000+12000]
...
2016-05-06T23:47:41.335077+00:00 WARNING kernel: [    5.354468] frecon(653): Frecon using drm driver i915, version 1.6, date(20150717), desc(Intel Graphics)
...

2016-05-06T16:51:09.052702-07:00 INFO kernel: [    1.246313] frecon[110]: segfault at 10 ip 00007fe1822595d8 sp 00007ffe2c75dce0 error 4 in frecon[7fe182254000+12000]

after that, there are a few logs like the following, probably the cause of unable to switch to VT2:

2016-05-06T16:51:36.232668-07:00 WARNING kernel: [   29.101792] frecon(507): Unable to set crtc: Invalid argument

And this does not look like kiosk specific to me though. Passing to dbehr@ to look with  issue 588425 .

This frecon crash
frecon[110]: segfault at 10 ip 00007fbcf349d5d8 sp 00007ffd18260290 
is unrelated to any display problems. It is because /dev/ptmx is not available when frecon is started first. It has been fixed here https://chromium-review.googlesource.com/#/c/344418/

This
frecon(507): Unable to set crtc: Invalid argument
seems like the problem, and is most likely caused by frecon not having DRM master so it cannot set video mode. It does look similar to  issue 588425 , this most likely happens when system is under load and Chrome does not give up DRM master when frecon asks it to.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Most likely dupe of  issue 610790 

This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Will reopen if we see this issue.