[Bug 87112] 24Hz (&23.976Hz) modes broken with recent drivers

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jul 22 11:46:55 PDT 2015


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

--- Comment #17 from Martin Andersen <martin.x.andersen at gmail.com> ---
Oh boy is my reply late..! (I was sure this bugreport had already been closed;
I never had time to follow this up properly last year around the time it was
logged - my sincerest apologies for that!)

Nevertheless (and in case it might still be of interest), I believe I narrowed
this nasty little bug down to the pre-2.99.917 versions of xf86-video-intel.
(Or perhaps, the 2.99.911 version itself as that is, i think, the only prior
version tested.)

I did numerous tests today on a Haswell system, running a 3.13.5-031305-generic
kernel, and was able to consistently reproduce the error with
xf86-video-intel-2.99.911 and eliminate it with xf86-video-intel-2.99.917.

I have provided a log with debug information from xf86-video-intel-2.99.917,
for the sake of completion. This is running the MATE desktop, btw. (which does
not use any compositing)

However (and despite this good news), the dual-output issue appears to have
been reincarnated in that it does not work - at all (i.e, no output) - with the
newer 4.0.x kernels (tested the kernel.ubuntu.com provided wily builds for
4.0.2, 4.0.4 & 4.0.9) in any 24Hz or 23.976Hz modes–only 50Hz & 60Hz modes
worked correctly on the secondary display (an Epson Projector–using the same
drivers and X config as the one which worked on 3.13.5). I consistently
reproduced this issue as well (and will open a separate bug report, if needed,
for it as I did also capture a debug log from the 2.99.917 driver.)

If not I'll provide it here, since there is some prior history for much of the
same issue.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150722/e36c5c55/attachment.html>


More information about the intel-gfx-bugs mailing list