[Reks] Display is corrupted after switching between VT2 and VT1. |
||||||||
Issue description
Version:7978.74.1
OS: ChromeOS
What steps will reproduce the problem?
(1) Power on sign in to the device.
(2) Open crosh window (Alt + Ctrl + t)
(3) Reboot the device
(4) Switch between VT2 and VT1 on sign-in screen.
Use (Ctrl + Alt + F1/F2) key combination.
(5) Sign in to the device.
What is the expected output?
Device should work properly.
What do you see instead?
Device display is corrupted.
Key board is not working in VT1.
Able to move the trackpad pointer, But click is not working.
Please use labels and text to provide additional information.
Note: Switching between modes stops after suspend resume.
,
Jun 1 2016
This is dev-mode specific and shouldn't block releases. Are you sure that step 2 (Ctrl-Alt-t) is necessary? That seems very unlikely since you're rebooting afterward.
,
Jun 1 2016
,
Jun 1 2016
Able to reproduce this issue on build 7978.74.0
,
Jun 1 2016
,
Jun 1 2016
Why is this back at Pri-1? Regular users aren't able to switch between virtual terminals.
,
Jun 1 2016
It is Pri-1 because: It is reproducible 100% It affects more than one device It disrupts UX and device is unusable Despite it is dev mode only, it is severe enough and could have side effects in normal mode. Somehow we did not catch it before, and if it was not yet in, we would mark RBS at least.
,
Jun 1 2016
@7: I really do not think there will be any effect in dev mode. It's definitely not p1.
,
Jun 1 2016
of course I meant "in non-dev mode" above..
,
Jun 1 2016
Actually, it was caught before - https://code.google.com/p/chrome-os-partner/issues/detail?id=51058
,
Jun 10 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/frecon/+/da3c010e2a84a30c0cc1dcaa6472012abcaffde8 commit da3c010e2a84a30c0cc1dcaa6472012abcaffde8 Author: Dominik Behr <dbehr@chromium.org> Date: Wed Jun 08 22:05:38 2016 frecon: keep master while frecon is active This change switches back to old frecon behavior where it would keep DRM master for whole time it was active. I thought we could only keep it for mode switch but it is also needed for framebuffer invalidation which is necessary on some hardware so we would need to set and drop it on every screen update. This change also centralizes DRM master set and drop in term foreground and background functions making it clear where it is set and dropped. There was also a case where when Chrome is under high load it becomes confused and still sends page flip requests even though frecon is active. In this case, if when frecon dropped master page flip succeeds and it appears the system is hanging (frecon is still processing keyboard events but static Chrome window is visible). BUG= chromium:610790 , chromium:588425 , chromium:616594 ,chrome-os-partner:51058 TEST=quickly switch between Chrome and frecon using ctrl-alt-< and ctrl-alt->\ while system is under high load. Change-Id: I651a89b307dcf31396ba52e2dcb605d2a7617cd9 Signed-off-by: Dominik Behr <dbehr@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/351010 Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> [modify] https://crrev.com/da3c010e2a84a30c0cc1dcaa6472012abcaffde8/main.c [modify] https://crrev.com/da3c010e2a84a30c0cc1dcaa6472012abcaffde8/term.c [modify] https://crrev.com/da3c010e2a84a30c0cc1dcaa6472012abcaffde8/drm.h [modify] https://crrev.com/da3c010e2a84a30c0cc1dcaa6472012abcaffde8/fb.c [modify] https://crrev.com/da3c010e2a84a30c0cc1dcaa6472012abcaffde8/drm.c
,
Jun 28 2016
,
Jul 8 2016
verified in 8172.62.0 / 51.0.2704.106 |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by sontis@chromium.org
, Jun 1 2016