[Bug 102022] [HSW] i915: null pointer in intel_dp_max_link_rate+0x5/0x80

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Aug 15 00:39:22 UTC 2017


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

--- Comment #7 from Dhinakaran Pandiyan <dhinakaran.pandiyan at intel.com> ---
(In reply to sassmann from comment #6)
> (In reply to Dhinakaran Pandiyan from comment #5)
> > (In reply to sassmann from comment #0)
> > > After switching display inputs on the monitor (Dell U3415W) the screen
> > > wouldn't come back from standby. Reproduced this with drm-tip
> > 
> > Thanks for filing this bug.
> > 
> > Can you please describe this a bit more in detail?
> 
> Sure, same setup as in bug #90963.
> Lenovo w541 docked in ThinkPad Dock with lid close (permanently).
> Dell U3415W display connected via DP as the only display.
> 
> > What was the display input switch that caused this?
> 
> The Monitor has 2 DP inputs. Switching input from the DP1, the w541 is
> connected to, to the other DP and back is sufficient to cause this problem.
> 
> > What was the DP mode in the monitor at that time?
> 
> Setting monitor to DP 1.1 and DP 1.2 both show the problem.
> 
> > How did you switch the display input?
> 
> Via monitor on-screen menu.
> 
> > Does this happen if you don't force the mode from cmdline?
> 
> That helps, I can switch DP inputs now without a crash! I had to force
> monitor input at some point as otherwise the external monitor wouldn't get
> detected. Now it seems to work better, so I probably can remove that quirk.
>  

Great! I think the problem is with the user space forcing a mode non-sink
connectors.


> > Can you please try this hack?
> 
> Already tried the patch from bug #90963, didn't help with this.

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


More information about the intel-gfx-bugs mailing list