[Bug 110030] New: regression bisected black screen with cursor

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Mar 13 12:24:06 UTC 2019


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

            Bug ID: 110030
           Summary: regression bisected black screen with cursor
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: 2kmm at gmx.de
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 143642
  --> https://bugs.freedesktop.org/attachment.cgi?id=143642&action=edit
Xorg log

Problem: when connecting two displays and starting X, both screens are just
black with a static (not blinking) text cursor in the top left corner. With
only one display (does not matter which one was disconnected) X starts normal
after reboot. Restarting X after connecting/disconnecting a display does not
change the behavior, the system has to be rebooted.

d8a648cae347dcad29dc976a1970f503eb27febf is the first bad commit
commit d8a648cae347dcad29dc976a1970f503eb27febf
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Fri Feb 15 12:30:19 2019 +0000

    drm/i915/fbdev: Actually configure untiled displays

    commit d179b88deb3bf6fed4991a31fd6f0f2cad21fab5 upstream.

With this commit applied an additional line shows in /var/log/Xorg.0.log:
[    31.581] (EE) modeset(0): failed to set mode: Invalid argument

Apart from this, the file is identical with or without the commit. No
differences in dmesg.

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


More information about the intel-gfx-bugs mailing list