[Bug 65757] [snb pch eDP regression] Screen sometimes remains black after mode change - old fast & narrow link is more stable

[bugzilla-daemon at freedesktop.org]

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

--- Comment #6 from Egbert Eich <eich at pdx.freedesktop.org> ---
(In reply to comment #5)
> (In reply to comment #4)
> > Quick thing to check on latest drm-intel-nightly, specifically
> > 
> > commit 8664281b64c457705db72fc60143d03827e75ca9
> > Author: Paulo Zanoni <paulo.r.zanoni at intel.com>
> > Date:   Fri Apr 12 17:57:57 2013 -0300
> > 
> >     drm/i915: report Gen5+ CPU and PCH FIFO underruns
> 
> Will do that.
> 
> > 
> > Do the fifo underrun reports fire up?

I do not see anything there. The only message regarding underruns is for
pipe underruns as quoted by Michal in the original report.

> > 
> > Also, as discussed in the meeting can you please test what happens when you
> > set the panel to eDP? Without that we also set up the HDMI connector, and
> > the i2c probing over HDMI is known to kill some eDP panels ...
> 
> When setting the panel eDP it will work: reason is that the bogus VBT eDP
> tables in the BIOS will mark the panel 1 lane and 18bpp, thus the frequency
> low enough that only a single lane is used.
> I will however disable the HDMI connector setup and the I2C probing on the
> eDP connector hacking the driver and see if this makes a difference.

I disabled HDMI initialization for testing by returning early from
intel_hdmi_init() ie:

@@ -1073,6 +1073,8 @@ void intel_hdmi_init(struct drm_device *dev, int
hdmi_reg,
 enum port port)
        struct drm_encoder *encoder;
        struct intel_connector *intel_connector;

+       return;
+
        intel_dig_port = kzalloc(sizeof(struct intel_digital_port),
GFP_KERNEL);

unfortunately the problem still occurs.

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