I was able to switch to VT2 terminal (using Ctrl+Alt+F2)

Can you describe better what did you have running on the device before this issue happened?
Did you have any external peripherals plugged?

Approx half an hour before the report:
2017-10-05T10:57:03.001910-07:00 WARNING kernel: [    1.846173] ------------[ cut here ]------------
2017-10-05T10:57:03.001915-07:00 WARNING kernel: [    1.846205] WARNING: CPU: 2 PID: 343 at /mnt/host/source/src/third_party/kernel/v3.18/drivers/gpu/drm/i915/intel_dp.c:4286 intel_dp_check_link_status+0xcf/0x143()
2017-10-05T10:57:03.001919-07:00 WARNING kernel: [    1.846236] WARN_ON_ONCE(!intel_dp->lane_count)
2017-10-05T10:57:03.001924-07:00 WARNING kernel: [    1.846247] Modules linked in: joydev
2017-10-05T10:57:03.001928-07:00 WARNING kernel: [    1.846270] CPU: 2 PID: 343 Comm: frecon Not tainted 3.18.0-16084-g087ebffcd47e #1
2017-10-05T10:57:03.001937-07:00 WARNING kernel: [    1.846289] Hardware name: Google Caroline/Caroline, BIOS Google_Caroline.7820.329.0 08/18/2017
2017-10-05T10:57:03.001947-07:00 WARNING kernel: [    1.846312]  0000000000000000 0000000062f67711 ffff880176e53b08 ffffffffa1ca19e0
2017-10-05T10:57:03.001952-07:00 WARNING kernel: [    1.846339]  0000000000000000 ffff880176e53b60 ffff880176e53b48 ffffffffa1663dbc
2017-10-05T10:57:03.001957-07:00 WARNING kernel: [    1.846364]  ffff880176e53b88 ffffffffa19e52ee ffff8801792010e8 0000000000000001
2017-10-05T10:57:03.001961-07:00 WARNING kernel: [    1.846389] Call Trace:
2017-10-05T10:57:03.001966-07:00 WARNING kernel: [    1.846404]  [<ffffffffa1ca19e0>] dump_stack+0x4e/0x71
2017-10-05T10:57:03.001971-07:00 WARNING kernel: [    1.846424]  [<ffffffffa1663dbc>] warn_slowpath_common+0x81/0x9b
2017-10-05T10:57:03.001976-07:00 WARNING kernel: [    1.846441]  [<ffffffffa19e52ee>] ? intel_dp_check_link_status+0xcf/0x143
2017-10-05T10:57:03.002072-07:00 WARNING kernel: [    1.846462]  [<ffffffffa1663e2b>] warn_slowpath_fmt+0x55/0x6b
2017-10-05T10:57:03.002076-07:00 WARNING kernel: [    1.846479]  [<ffffffffa19e52ee>] intel_dp_check_link_status+0xcf/0x143
2017-10-05T10:57:03.002081-07:00 WARNING kernel: [    1.846497]  [<ffffffffa19e5b52>] intel_dp_detect+0x556/0x8da
2017-10-05T10:57:03.002086-07:00 WARNING kernel: [    1.846517]  [<ffffffffa19366a0>] drm_helper_probe_single_connector_modes_merge_bits+0xc9/0x3bc
2017-10-05T10:57:03.002090-07:00 WARNING kernel: [    1.846540]  [<ffffffffa19369a6>] drm_helper_probe_single_connector_modes+0x13/0x15
2017-10-05T10:57:03.002095-07:00 WARNING kernel: [    1.846561]  [<ffffffffa194faa0>] drm_mode_getconnector+0x10d/0x36b
2017-10-05T10:57:03.002102-07:00 WARNING kernel: [    1.846581]  [<ffffffffa1944197>] drm_ioctl+0x3d3/0x451
2017-10-05T10:57:03.002106-07:00 WARNING kernel: [    1.846597]  [<ffffffffa194f993>] ? drm_mode_getcrtc+0x116/0x116
2017-10-05T10:57:03.002111-07:00 WARNING kernel: [    1.846663]  [<ffffffffa176228e>] do_vfs_ioctl+0x399/0x460
2017-10-05T10:57:03.002115-07:00 WARNING kernel: [    1.846685]  [<ffffffffa17623af>] SyS_ioctl+0x5a/0x7f
2017-10-05T10:57:03.002145-07:00 WARNING kernel: [    1.846703]  [<ffffffffa1636850>] ? do_page_fault+0xc/0xe
2017-10-05T10:57:03.002150-07:00 WARNING kernel: [    1.846724]  [<ffffffffa1ca6ddc>] system_call_fastpath+0x1c/0x21
2017-10-05T10:57:03.002159-07:00 WARNING kernel: [    1.846740] ---[ end trace 3cd9f63a1036e534 ]---
2017-10-05T10:57:03.002177-07:00 WARNING kernel: [    1.847009] frecon(343): Frecon using drm driver i915, version 1.6, date(20150717), desc(Intel Graphics)

There were not any external peripherals connected as such (like no external drives/ external monitor connected. I had signed in on user and device was idle for few minutes.

Any crash records on chrome://crashes?
I see crash/d73b115df37c4f19 from Oct 4th. Anything newer?

Could be a duplicate of  issue 741031 .

Hi Kalin, I could not check any of the crash records because of device freeze. Prior to the freeze, I had performed AU and signed in. 

Do you mean it is consistently hanging after sign-in?

Few more lines in messages on crash_reprter side

2017-10-05T10:57:08.241263-07:00 WARNING crash_reporter[2098]: [user] Received crash notification for tzdatacheck[2051] sig 6, user 656360 (ignoring - PID filtered out)
2017-10-05T10:57:08.241486-07:00 WARNING crash_reporter[2098]: [ARC] Received crash notification for tzdatacheck[2051] sig 6, user 656360 (handling)
2017-10-05T10:57:08.243660-07:00 INFO crash_reporter[2098]: State of crashed process [2051]: S (sleeping)
2017-10-05T10:57:08.246506-07:00 ERR crash_reporter[2098]: Could not get active user sessions, using default.

Device didn't hang consistently. But twice, I observed this kind of hang and had to reboot my machine afterwards. On and off I was using this device and so device was idle few times. Once I started using it from idle state, observed UI freeze and device didn't recover from the freeze. But, I could see only mouse movements.

If you recover from the freeze, and sign-in to the device, check the content of chrome://crashes page in browser, and see if there is a Crash record for the time the issue was present.

Sure, I will share the crash details once after I could reproduce this issue one more time.

Same issue on Eve device. 10009.0.0, 63.0.3230.0

No external peripherals were connected to the device. Just kept the device aside for some time and then the UI froze.

Touch and keyboard inputs are not working. Only mouse cursor movements are visible. But able to switch to VT2. 

Attached device logs.

Deleted: debug-logs_20171011-115359.tgz 2.2 MB

debug-logs_20171011-115359.tgz 2.2 MB Download

ChromeOS_ARC crash/c5e7cf3d7bebdc6a found in the #10 logs, same as the one in #4. 
Thread 0 (id: 19) CRASHED [SIGABRT @ 0x00000000 ]
Stack Quality100%Show frame trust levels
0x00007d530a938567	(libc.so + 0x0008d567 )	tgkill
0x00007d530a935021	(libc.so -bionic/libc/bionic/pthread_kill.cpp:45 )	pthread_kill
0x00007d530a8db1e1	(libc.so -bionic/libc/bionic/raise.cpp:34 )	raise
0x00007d530a8d385d	(libc.so -bionic/libc/bionic/abort.cpp:47 )	abort
0x00007d530a81b563	(libbase.so -logging.cpp:404 )	android::base::LogMessage::~LogMessage()
0x000055638142c016	(tzdatacheck -tzdatacheck.cpp:57 )	readHeader(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, char*, unsigned long)
0x000055638142b470	(tzdatacheck -tzdatacheck.cpp:191 )	main
0x00007d530a8c79b4	(libc.so -bionic/libc/bionic/libc_init_dynamic.cpp:109 )	__libc_init
0x000055638142b207	(tzdatacheck + 0x00001207 )	_start

abodeti@ filed b/67637900

Saw a similar issue on Eve M62-9901.41.0 

Sample traceback below,
14395 2017-10-11T12:12:40.418038-07:00 WARNING kernel: [    7.439060] Hardware name: Google Eve/Eve, BIOS Google_Eve.9584.76.0 08/12/2017
  14396 2017-10-11T12:12:40.418039-07:00 WARNING kernel: [    7.439062]  0000000000000286 164cf4be95395eeb ffff880065e7be10 ffffffff926941ce
  14397 2017-10-11T12:12:40.418039-07:00 WARNING kernel: [    7.439068]  0000000000000000 0000000000000009 ffff880065e7be48 ffffffff92469858
  14398 2017-10-11T12:12:40.418040-07:00 WARNING kernel: [    7.439073]  ffffffff92483c8e ffff88024433c108 ffff88024433c108 ffffffff92483c5d
  14399 2017-10-11T12:12:40.418041-07:00 WARNING kernel: [    7.439077] Call Trace:
  14400 2017-10-11T12:12:40.418042-07:00 WARNING kernel: [    7.439083]  [<ffffffff926941ce>] dump_stack+0x4d/0x63
  14401 2017-10-11T12:12:40.418042-07:00 WARNING kernel: [    7.439088]  [<ffffffff92469858>] warn_slowpath_common+0x9f/0xb8
  14402 2017-10-11T12:12:40.418043-07:00 WARNING kernel: [    7.439091]  [<ffffffff92483c8e>] ? kthread_worker_fn+0x31/0x1a6
  14403 2017-10-11T12:12:40.418044-07:00 WARNING kernel: [    7.439094]  [<ffffffff92483c5d>] ? kthread_park+0x52/0x52
  14404 2017-10-11T12:12:40.418045-07:00 WARNING kernel: [    7.439097]  [<ffffffff9246996a>] warn_slowpath_null+0x1a/0x1c
  14405 2017-10-11T12:12:40.418045-07:00 WARNING kernel: [    7.439099]  [<ffffffff92483c8e>] kthread_worker_fn+0x31/0x1a6
  14406 2017-10-11T12:12:40.418046-07:00 WARNING kernel: [    7.439102]  [<ffffffff92483c5d>] ? kthread_park+0x52/0x52
  14407 2017-10-11T12:12:40.418047-07:00 WARNING kernel: [    7.439104]  [<ffffffff92483c5d>] ? kthread_park+0x52/0x52
  14408 2017-10-11T12:12:40.418048-07:00 WARNING kernel: [    7.439107]  [<ffffffff92483be1>] kthread+0x12c/0x134
  14409 2017-10-11T12:12:40.418048-07:00 WARNING kernel: [    7.439110]  [<ffffffff92483ab5>] ? kthread_parkme+0x24/0x24
  14410 2017-10-11T12:12:40.418049-07:00 WARNING kernel: [    7.439114]  [<ffffffff92b05eaf>] ret_from_fork+0x3f/0x70
  14411 2017-10-11T12:12:40.418050-07:00 WARNING kernel: [    7.439116]  [<ffffffff92483ab5>] ? kthread_parkme+0x24/0x24
  14412 2017-10-11T12:12:40.418050-07:00 WARNING kernel: [    7.439119] ---[ end trace b06abbe02d661411 ]---
  14413 2017-10-11T12:12:40.431972-07:00 ERR laptop-mode[2202]: Couldn't acquire lock. Retrying.... PID is 2133\n
  14414 2017-10-11T12:12:40.446017-07:00 WARNING kernel: [    7.467909] HDMI HDA Codec ehdaudio0D2: Max dais supported: 3
  14415 2017-10-11T12:12:40.616027-07:00 NOTICE kernel: [    7.637854] audit: type=1400 audit(1507749160.614:7): avc:  denied  { search } for  pid=1851 comm="logd" name="data" dev="dm-0" ino=73907 scontext=u:r:logd:s0 tcontext=u:object_r:unlabeled:s0 tclass=dir permissive=0
  14416 2017-10-11T12:12:40.629016-07:00 NOTICE kernel: [    7.650878] audit: type=1400 audit(150774

Will report, if it happens on latest M62. 
Logs attached.

Issue repro'd on M62-BETA-CHROMEOS-2 (9901.44.0, 62.0.3202.52). Checked on eve, caroline. Adding RBB label

not repo in last beta, diff https://crosland.corp.google.com/log/9901.35.0..9901.44.0

I'm seeing the issue on Chrome 62.0.3202.52/CrOS 9901.44.0 - Spring.  After idle for 10~12 mins, UI is freezing. Only mouse cursor movements are working. 

Deleted: debug-logs_20171011-162514 359 KB

debug-logs_20171011-162514 359 KB View Download

-puthik as I don't see this being a PSR problem.

Given this was seen on peach-pi, it is not kernel specific, PSR, or related to ARC++. 

If VT2 is still working, the system is at least still alive, this implies something is stuck on the Chrome side most likely.

Chrome side diff is https://chromium.googlesource.com/chromium/src/+log/62.0.3202.43..62.0.3202.52?pretty=fuller&n=10000

Do we have any steps to repro?

Is this related to  Issue 769570  or Issue 763736

Observed UI freeze on daisy device too on Chrome 62.0.3202.52/CrOS 9901.44.0. Logs are attached.

Deleted: debug-logs_20171011-171831.tgz 191 KB

debug-logs_20171011-171831.tgz 191 KB Download

Any clues to a repro?

xiyuan@ can you take a look at the logs and see if anything stands out?

mkarkada: What do you mean by idle? Was the screen off? If the screen went off, and when you tried to move the cursor again you got the old content and the cursor moving (GLRenderer stopped producing new content), this is likely a dup of  crbug.com/769570 
It should be fixed now.

From my comment in #25, device was in suspended state. When I resumed it, I could just move the mouse but UI had froze. 
From my comment in #3, device was idle for sometime and had to wake up the device, when I saw this issue. I think, device was in sleep mode, but don't remember exactly.

Thank you for the answer.
This seems a dup of  crbug.com/769570 .
Please re-open it if you can still reproduce it on ToT.