Bug 91771 - Microsoft Surface 3 screen goes black, and appears to freeze when i915.modeset=1
Summary: Microsoft Surface 3 screen goes black, and appears to freeze when i915.modeset=1
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-27 05:54 UTC by Stephen Just
Modified: 2017-07-24 22:45 UTC (History)
2 users (show)

See Also:
i915 platform: BSW/CHT
i915 features:


Attachments
Output of lshw (9.03 KB, text/plain)
2015-08-27 05:54 UTC, Stephen Just
no flags Details
full dmesg output (452.93 KB, text/plain)
2015-09-07 17:52 UTC, Stephen Just
no flags Details

Description Stephen Just 2015-08-27 05:54:10 UTC
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.
Comment 1 Stephen Just 2015-08-27 05:54:49 UTC
Created attachment 117945 [details]
Output of lshw
Comment 2 Jani Nikula 2015-08-27 07:49:25 UTC
Please attach dmesg all the way from boot with drm.debug=14 module parameter enabled, with modeset enabled. Maybe you need to figure out how to use netconsole or usb console or how to ssh in or something to get this info.
Comment 3 Stephen Just 2015-09-07 17:52:21 UTC
Created attachment 118127 [details]
full dmesg output

I finally have a dmesg for you.
I booted with module i915 blacklisted, then connected over ssh, and ran 'modprobe i915'. Then I captured the dmesg over ssh - so I guess the kernel didn't crash completely, which is a good thing.
Comment 4 Stephen Just 2015-09-20 03:33:51 UTC
This looks like he same thing as the bug at https://bugzilla.kernel.org/show_bug.cgi?id=97941 It looks like it's getting more attention over there.
Comment 5 Jani Nikula 2016-04-18 15:27:10 UTC
Surface 3 is now much healthier running drm-intel-nightly branch of 
http://cgit.freedesktop.org/drm-intel

Thanks for the report, I'm closing this one as fixed. As specific new issues arise, please file new bugs on them.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.