<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED FIXED - [CFL] Screen goes blank right after boot." href="https://bugs.freedesktop.org/show_bug.cgi?id=104139#c30">Comment # 30</a> on <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED FIXED - [CFL] Screen goes blank right after boot." href="https://bugs.freedesktop.org/show_bug.cgi?id=104139">bug 104139</a> from <a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>(In reply to Pavel Nakonechnyi from <a href="show_bug.cgi?id=104139#c29">comment #29</a>) > (In reply to Jani Nikula from <a href="show_bug.cgi?id=104139#c28">comment #28</a>) > > (In reply to Timo Aaltonen from <a href="show_bug.cgi?id=104139#c27">comment #27</a>) > > > right, I replied to the patch thread asking if it should be sent for stable, > > > but got no reply > > > > Yeah, sorry about that. The relevant commits are in v4.16: > > > > 6e3322c226f1 ("drm/i915/cnp: Properly handle VBT ddc pin out of bounds.") > > f24c606c21a8 ("drm/i915/cnp: Ignore VBT request for know invalid DDC pin.") > > > > I've made a stable backport request for v4.15. > > Thank you. > > However, in my personal case (Dell 5590 laptop with "Intel Corporation UHD > Graphics 620 (rev 07)" card), the mentioned patches not enough to solve the > problem. > > I experience the same error as in the original bug report. The only solution > that works for me for v4.16 and v4.14 kernels is to apply the patch from > <a href="https://patchwork.kernel.org/patch/10003565/">https://patchwork.kernel.org/patch/10003565/</a> "drm/i915: check pin validity > of VBT configurationlogin". > > From my point of view "6e3322c226f1" and "f24c606c21a8" contain slightly > less quirks comparing to the patch that helped me. > > Could someone with good knowledge of this subsystem decide if it should also > be included into the mainline/stable? The patch is not even upstream. The two commits apparently helped the original reporter, so it seems to me you have a different root cause. Please file a new bug, add dmesg with drm.debug=14, attach /sys/kernel/debug/dri/0/i915_vbt. Are you doing UEFI boot? If not, please try.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>