[Bug 101111] [Regression] backlight flickering/display artifacting on Broadwell integrated graphics with 4.12-rc1

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Sep 18 20:31:39 UTC 2017


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

--- Comment #57 from Mark Spencer <n7u4722r35 at ynzlx.anonbox.net> ---
(In reply to Jani Nikula from comment #56)
> There's a distinction between a) enabling PSR to actively work on fixing
> issues related to it, and b) enabling PSR because some forum said you should
> and then filing issues here because it doesn't work out for you.


I didn't fill myself any new issue about this. I only joined discussion which
already started here and on previous related bugreport. Also I have PSR in
working state for more than a year with dirtyfix I created myself. Meanwhile I
provided all information I can everytime one of developers asked. I recompiled
my kernel with every patch that was proposed, tested it and posted logs.


> We've disabled PSR by default because there have been so many issues with
> it, and we can't handle the influx of bugs. We keep fixing stuff in the
> background, but at the same time we close PSR bugs as not supported. For
> example, in the case of this bug, it took until comment #44 to realize this
> is a PSR related bug. You also insisted on merging what would have been the
> completely wrong patch, and would have made debugging future PSR problems
> even harder. My gut feeling in comment #21 was spot on.


The problem is that I didn't submit those two bugreports myself and they
weren't very clear in my opinion. I tried bring some new information but it was
probably lost in translation. I think PSR was enabled in every log I posted. I
wrote explicitly about PSR in
https://bugs.freedesktop.org/show_bug.cgi?id=97918#c22 in February. Honestly I
thought that devs knew this issue is strictly connected to PSR.

Also that was You who insisted on merging wrong solution
https://bugs.freedesktop.org/show_bug.cgi?id=101111#c5 . My first post in this
topic is after that comment of yours.

> So there'll be a happy ending to this bug, the driver will get a bit better
> now, and we're a bit closer to enabling PSR, thank you for that. But perhaps
> you'll see that there's a reason we generally close what we think are
> category b) bugs as not supported.

I agree with you but I hope you reconsider my role after reading my
explanations above. I believe everything is clear now. Many thanks for you and
all the rest of the devs who helped.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170918/f4e77d5e/attachment-0001.html>


More information about the intel-gfx-bugs mailing list