Re: Backporting skl_update_other_pipe_wm intel drm fixes to the Fedora 4.6 kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 17-06-16 22:37, David Airlie wrote:


----- Original Message -----
From: "Hans de Goede" <hdegoede@xxxxxxxxxx>
To: kernel@xxxxxxxxxxxxxxxxxxxxxxx
Cc: "Lyude" <cpaul@xxxxxxxxxx>, "Rob Clark" <rclark@xxxxxxxxxx>
Sent: Saturday, 18 June, 2016 1:52:07 AM
Subject: Backporting skl_update_other_pipe_wm intel drm fixes to the Fedora 4.6 kernel

Hi Fedora kernel team,

If you look at:

https://retrace.fedoraproject.org/faf/problems/

And look for skl_update_other_pipe_wm there, you will see
that it is completely dominating the problem report stats
(listed 4 times on the first page, 5 times on the second).

I talked to #intel-gfx, they said the warn was pretty harmless and we could
also just propose a stable patch to drop that warning.

The warning is mostly harmless, except in the cases where it isn't
when using display-port displays (including edp for laptop panels),
the warning is actually not harmless (it causes display fifo
under-runs leading to the lcd panel flickering to black and back
to the picture a few times every 5 minutes or so).

We've reports of similar flickering issues with external dp
monitors on skylake.

And according to Lyude it can even cause hangs in some cases.

Regards,

Hans





Though I'm also okay with backporting fixes.

Dave.

As such I'm thinking about backporting the patches:
http://www.spinics.net/lists/intel-gfx/msg95595.html

To the Fedora 4.6 kernel.

Some of the reported problems are only a WARN_ON triggering,
but there are also quite a few cases of actually wrong
watermark settings causing various real problems.

These patches have been around for a long time, but they missed
the 4.6 merge window, and then also the 4.7 merge window, they
are in next now. But IMHO we should grab them now since the
problems they are causing are too big to wait for 4.8
hitting Fedora.

So I would like to backport these to the 4.6 Fedora kernel
and have this completed before we start pushing 4.6 updated
to updates-testing. This way we can use the entire Fedora 4.6
testing phase to also test the backported fixes.

Before I spend time on this, does this sound like a good
plan ?  I've already discussed this within the graphics
team and the consensus there seems to be that this is a good
idea.

Regards,

Hans
_______________________________________________
kernel mailing list
kernel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/kernel@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
kernel mailing list
kernel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/kernel@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [USB]     [Asterisk PBX]

  Powered by Linux