[Bug 99469] Unable to switch to console mode by press Ctrl-Alt-F2 on Chromebook with drm-intel-nightly kernel
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue May 23 06:43:58 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=99469
jenny cao <jenny.q.cao at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #7 from jenny cao <jenny.q.cao at intel.com> ---
this issue could be reproduced on latest chrome os image + upstream
kernel(drm-tip branch)
kernel version: 4.12.0-rc2-14320-gec077216f693-dirty
OS image version:9559.0.2017_05_23_1122
Chromium browser version: 60.0.3101.0
Firmware version: Google_Lars.7829,127.0
The screen show black when I use "Ctrl-Alt-F2" to switch to console.
dmesg shows :
[ 124.924367] frecon(260):
[ 124.924378] Could not set master when switching to foreground Invalid
argument.
[ 124.924537] DEBUG: tsm_screen:
[ 124.924540] new screen
[ 124.924566] DEBUG: tsm_vte:
[ 124.924569] new vte object
and not able to switch back to UI by "Ctrl-Alt-F1",
dmesg log shows:
[ 125.891071] frecon(260):
[ 154.012310] frecon(260):
[ 154.012324] Chrome failed to take display ownership. Trying again.
[ 154.514180] frecon(260):
[ 154.514187] Chrome failed to take display ownership. Trying again.
[ 155.016262] frecon(260):
[ 155.016269] Chrome failed to take display ownership. Trying again.
[ 155.518382] frecon(260):
[ 163.208521] frecon(260):
[ 163.208537] Could not set master when switching to foreground Invalid
argument.
[ 163.563262] frecon(260):
[ 163.563272] Unable to set crtc: Permission denied
[ 163.563510] frecon(260):
[ 163.563514] drmModeDirtyFB failed: Permission denied
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170523/0e94ddca/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list