[Bug 91436] New: PSR screen freeze

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91436

            Bug ID: 91436
           Summary: PSR screen freeze
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: ivan.mitev at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 117306
  --> https://bugs.freedesktop.org/attachment.cgi?id=117306&action=edit
dmesg, booting undocked on bat, PSR=1, FBC=0

Enabling PSR -> screen freezes at boot a bit after modesetting, but not exactly
at modesetting since the resolution is changed to a high one and I can see
graphics.

Hardware: lenovo T450s, model 20BX000TBM (see attached dmidecode and lspci_vv).
OS: Fedora 22, fully updated (as of 2015-07-23)
Kernel: git drm-intel-nightly (as of 2015-07-22 evening). .config attached
(config.drm-intel).

Tests (attached dmesg -c > ...):

dmesg-boot_undocked_psr0_fbc1:
- boot with laptop undocked (but on AC), enable_psr=0, enable_psr=1
- laptop seems to work fine

dmesg-boot_undocked_psr1_fbc0:
- boot with laptop undocked (but on AC), enable_psr=1, enable_psr=0
- screen freezes at encrypted luks password (fedora's lock image shows up, with
the password field, but there's no screen feedback to keyboard events).
- laptop is responsive though, so I can blindly switch to a vt, log as root,
and dump dmesg to a file.

dmesg-0-boot_undocked_bat_psr1_fbc0:
- boot with laptop undocked (on battery), enable_psr=1, enable_psr=0
- same behavior as on AC (boot_undocked_psr1_fbc0).
dmesg-0-boot_undocked_bat_psr1_fbc0-after-suspend: I thought of another test:
blindly suspended laptop, resumed, and laptop's panel is now OK and laptop is
usable

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150723/a0ce13ce/attachment.html>