Bug 94299 - Missing secondary display with Kernel 4.4 on Sandybridge
Summary: Missing secondary display with Kernel 4.4 on Sandybridge
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-26 01:33 UTC by Robert Kaiser
Modified: 2017-07-28 14:37 UTC (History)
3 users (show)

See Also:
i915 platform: SNB
i915 features: display/HDMI


Attachments
dmesg, kernel 4.4.0 (65.10 KB, text/plain)
2016-02-26 01:33 UTC, Robert Kaiser
no flags Details
dmesg, kernel 4.3.3 (66.33 KB, text/plain)
2016-02-26 01:34 UTC, Robert Kaiser
no flags Details
xrandr --verbose, kernel 4.4.0 (4.96 KB, text/plain)
2016-02-26 01:34 UTC, Robert Kaiser
no flags Details
xrandr --verbose, kernel 4.3.3 (8.50 KB, text/plain)
2016-02-26 01:35 UTC, Robert Kaiser
no flags Details
kernel/DRM syslog messages from drm.debug=0x0e, kernel 4.4.1 (121.56 KB, text/plain)
2016-02-27 19:31 UTC, Robert Kaiser
no flags Details
kernel/DRM syslog messages from drm.debug=0x0e, kernel 4.3.3 (134.78 KB, text/plain)
2016-02-27 19:32 UTC, Robert Kaiser
no flags Details

Description Robert Kaiser 2016-02-26 01:33:37 UTC
Created attachment 121970 [details]
dmesg, kernel 4.4.0

With the openSUSE Tumbleweed update to kernel 4.4, my secondary display went dark.
This is on a Sandybridge graphics system (i7-2600K) with an Intel mainboard (DH67CL), the same problem persists with 4.4.1 and 4.5-rc1 kernels from OBS (Kernel:Stable and Kernel:HEAD), while a 4.3.3 from home:tiwai:kernel:4.3 makes the display connected to "HDMI2" (actually the DVI connector) work again fine - the main display on "HDMI1" (HDMI connector of the mainboard) works fine with all those kernel variants.

I'm attaching dmesg and xrandr --verbose output for both 4.4.0 and 4.3.3 kernels.
Comment 1 Robert Kaiser 2016-02-26 01:34:15 UTC
Created attachment 121971 [details]
dmesg, kernel 4.3.3
Comment 2 Robert Kaiser 2016-02-26 01:34:45 UTC
Created attachment 121972 [details]
xrandr --verbose, kernel 4.4.0
Comment 3 Robert Kaiser 2016-02-26 01:35:06 UTC
Created attachment 121973 [details]
xrandr --verbose, kernel 4.3.3
Comment 4 Robert Kaiser 2016-02-27 19:31:50 UTC
Created attachment 122007 [details]
kernel/DRM syslog messages from drm.debug=0x0e, kernel 4.4.1

As requested in https://bugzilla.opensuse.org/show_bug.cgi?id=968354#c1 I am also attaching a |grep -iE "drm|kernel"| of all syslog messages I got with drm.debug=0x0e on a non-working (4.4.1) as well as the working (4.3.3) kernel.
Comment 5 Robert Kaiser 2016-02-27 19:32:18 UTC
Created attachment 122008 [details]
kernel/DRM syslog messages from drm.debug=0x0e, kernel 4.3.3
Comment 6 Robert Kaiser 2016-03-18 18:39:09 UTC
I don't want to sound ungrateful, I see flags are being added here, is anyone actually working on this or investigating it? Or should I provide some other data from my system?

This currently disrupts my work as I need to run the older 4.3.3 kernel but some modules I'd need are only compiled for current kernels by my distro.
Comment 7 Robert Kaiser 2016-05-28 10:21:34 UTC
I always was a big fan of Intel, but I guess I'll have to buy a new computer and avoid Intel products there as much as possible, as this is impairing my productivity significantly. Of course, I will also need to talk publicly about how Intel fails to support its products and customers, sadly. I would have preferred to see this bug fixed and everyone be happy, but it's been more than 3 months and I can't afford running into such a show-stopper in the future (and I have to assume that with Intel, you have to expect that happening again).
Comment 8 Robert Kaiser 2016-06-07 10:34:23 UTC
Actually, I guess I have to apologize for the last comment. I just tried kernel 4.6.1 and the second screen works there!
If that's because of an explicit bug fix, would have been nice to get notified in here about that as it's great that it works right now.


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.