[Bug 91434] New: 23.976Hz & 24Hz modes broken on dual-display with recent (4.0.x) kernels
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Jul 22 13:47:31 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=91434
Bug ID: 91434
Summary: 23.976Hz & 24Hz modes broken on dual-display with
recent (4.0.x) kernels
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: martin.x.andersen at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
This is a somewhat similar issue to #87112, which was recently identified as
being related to the xf86-video-intel driver. However this bug relates to
drm/i915 changes in recent 4.0.x kernels (tested several kernel.ubuntu.com
provided wily builds for 4.0.2, 4.0.4 & 4.0.9; both generic and lowlatency
versions. They all exhibit the same problem.)
Problem description:
Switching to 24Hz or 23.976Hz modes (which previously worked using the same X
setup and drivers) on a secondary display produces no signal. The secondary
display is able to output only 50 & 60Hz modes.
Kernel: 4.0.9-040009-lowlatency #201507212131 SMP PREEMPT Wed Jul 22 01:41:54
UTC 2015 x86_64
Correct behaviour is observed by reverting to 3.13.5 & 3.18.5. (w/ no other
changes performed)
vainfo:
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_38
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.38 (libva 1.6.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell - 1.6.0
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264MultiviewHigh : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileH264StereoHigh : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileH264StereoHigh : VAEntrypointEncSlice
I am attaching a full Xorg.0.log when running the latest xf86-video-intel
driver (2.99.917), compiled with '--enable-debug=full' on this Haswell (Intel
Iris Graphics 5100) system. I am also attaching similar output from a working
system (although the output is more limited)
Steps done on the client side while debug output was running: (steps not
included are logging in from MDM and starting a Gnome Mate session) –
martin at meraxes ~ $ xrandr --output HDMI2 --rate 24 --mode 1920x1080
martin at meraxes ~ $
martin at meraxes ~ $ xrandr -q
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
286mm x 179mm
2560x1600 60.0 +
2048x1536 60.0
1920x1440 60.0
1856x1392 60.0
1792x1344 60.0
1920x1200 60.0
1920x1080 59.9*
1600x1200 60.0
1680x1050 60.0 59.9
1600x1024 60.2
1400x1050 60.0
1280x1024 60.0
1440x900 59.9
1280x960 60.0
1360x768 59.8 60.0
1152x864 60.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 1920x1080+1920+0 (normal left inverted right x axis y axis)
1600mm x 900mm
1920x1080 60.0 + 50.0 59.9 24.0* 24.0
1920x1080i 60.1 50.0 60.0
1280x720 60.0 50.0 59.9
1440x576 50.0
1440x480 60.0 59.9
720x576 50.0
720x576i 50.1
720x480 60.0 59.9
720x480i 60.1 60.1
640x480 60.0 59.9
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
martin at meraxes ~ $
martin at meraxes ~ $ xrandr --output HDMI2 --rate 23.976 --mode 1920x1080
martin at meraxes ~ $ xrandr --output HDMI2 --rate 25 --mode 1920x1080
martin at meraxes ~ $
martin at meraxes ~ $ xrandr --output HDMI2 --rate 50 --mode 1920x1080
martin at meraxes ~ $
martin at meraxes ~ $ xrandr -q
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
286mm x 179mm
2560x1600 60.0 +
2048x1536 60.0
1920x1440 60.0
1856x1392 60.0
1792x1344 60.0
1920x1200 60.0
1920x1080 59.9*
1600x1200 60.0
1680x1050 60.0 59.9
1600x1024 60.2
1400x1050 60.0
1280x1024 60.0
1440x900 59.9
1280x960 60.0
1360x768 59.8 60.0
1152x864 60.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 1920x1080+1920+0 (normal left inverted right x axis y axis)
1600mm x 900mm
1920x1080 60.0 + 50.0* 59.9 24.0 24.0
1920x1080i 60.1 50.0 60.0
1280x720 60.0 50.0 59.9
1440x576 50.0
1440x480 60.0 59.9
720x576 50.0
720x576i 50.1
720x480 60.0 59.9
720x480i 60.1 60.1
640x480 60.0 59.9
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
martin at meraxes ~ $
martin at meraxes ~ $ xrandr --output HDMI2 --rate 24.0 --mode 1920x1080
martin at meraxes ~ $
martin at meraxes ~ $ xrandr --output HDMI2 --rate 60 --mode 1920x1080
--
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/20150722/ef680b68/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list