[Bug 91771] New: Microsoft Surface 3 screen goes black, and appears to freeze when i915.modeset=1

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Aug 26 22:54:10 PDT 2015


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

            Bug ID: 91771
           Summary: Microsoft Surface 3 screen goes black, and appears to
                    freeze when i915.modeset=1
           Product: DRI
           Version: DRI 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: stephenjust at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

On the Microsoft Surface 3 (non-pro), when booting Linux, the screen goes
black, and the entire device becomes unresponsive. Because the only output
device is the screen on this tablet, I'm gauging unresponsiveness by the
attached keyboard no longer changing state when Caps Lock or other keys with
LEDs are pressed.

The system can be booted successfully without the system freezing with kernel
parameter i915.modeset=0, but obviously that means all I get is a framebuffer
video device, which is not desirable.

I need a little bit of direction as to how I can collect any sort of useful
information for you. Because the device freezes and the display shuts off, I
can't really even copy logs off the device when the problem occurs.

Any suggestions would be appreciated.

I'm running linux kernel 4.2.0-rc6 with changes merged in from drm-intel, but
I'd switch over to drm-intel-nightly to do any data collection.

-- 
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/20150827/a82fd7b0/attachment.html>


More information about the intel-gfx-bugs mailing list