<div dir="ltr">Any further thoughts on this issue?</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jan 20, 2013 at 1:17 PM, Jonathan Adamczewski <span dir="ltr"><<a href="mailto:jonathan.adamczewski@gmail.com" target="_blank">jonathan.adamczewski@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yanking and re-plugging the DP cable did work when I tried it. My recollection is that there have been times when it hasn't worked, though it's possible there was something else going on (user error, etc...)<br>
<div><br></div><div>Regarding the "hotplug interrupt for DP" message: that /does not/ fire when the screen goes black. It did fire when yanking the cable, and again when re-plugging.<br></div><div><br></div><div>
fwiw, when the screen goes blank, it does not appear to drop to a low power or no-sync state: the power light remains solid (if I disable the monitor with xrandr etc, the power light will pulse). Sometimes the picture will return with no intervention required and there is no apparent delay while the monitor "resyncs", it's instant off, instant on. The screen can go black for periods <1 second. If video is still playing, it's likely to go black a second time and to not return.<br>
<br></div><div>Many thanks for you help so far - what's my next course of action?<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888"><div><br></div><div>j.<br>
</div><div><br></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jan 20, 2013 at 3:52 AM, Daniel Vetter <span dir="ltr"><<a href="mailto:daniel@ffwll.ch" target="_blank">daniel@ffwll.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hm, it's a DP screen which I've suspected (those are the kind who can<br>
lose sync and go black). But somehow we don't get any hotplug event<br>
when this happens - so the driver has no idea that the link went bad<br>
and that we need to retrain. Can you please test this with this<br>
snippet:<br>
<br>
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c<br>
index 1492706..5e91242 100644<br>
--- a/drivers/gpu/drm/i915/intel_dp.c<br>
+++ b/drivers/gpu/drm/i915/intel_dp.c<br>
@@ -2580,6 +2580,8 @@ intel_dp_hot_plug(struct intel_encoder *intel_encoder)<br>
{<br>
struct intel_dp *intel_dp = enc_to_intel_dp(&intel_encoder->base);<br>
<br>
+ printk("hotplug interrupt for DP\n");<br>
+<br>
intel_dp_check_link_status(intel_dp);<br>
}<br>
<br>
Also please check whether yanking and re-plugging the DP cable will<br>
restore the display - it should.<br>
-Daniel<br>
<br>
On Sun, Jan 20, 2013 at 5:45 AM, Jonathan Adamczewski<br>
<div><div><<a href="mailto:jonathan.adamczewski@gmail.com" target="_blank">jonathan.adamczewski@gmail.com</a>> wrote:<br>
> Thanks for the reply, Daniel.<br>
><br>
> Full traces are attached. I booted the system, ran dmesg after logging in<br>
> through kdm.<br>
><br>
> (Then I left the system while doing some other errands, hence the gap in<br>
> time)<br>
><br>
> I then started firefox, went to youtube and started watching some 4K<br>
> resolution videos. The external screen went black in less than a minute.<br>
> Second file is dmesg run after that - there doesn't appear to be much to<br>
> see...<br>
><br>
> There was nothing in dmesg that correlated directly with the screen going<br>
> black. I've validated this by triggering the screen going black several<br>
> times (that's not in the attached log, though) - there was never anything in<br>
> dmesg that happened at the same time or that happened for tens of seconds<br>
> thereafter.<br>
><br>
><br>
> What's the next step for gathering information here?<br>
><br>
> Many thanks<br>
><br>
> Jonathan.<br>
><br>
><br>
><br>
><br>
><br>
> On Sat, Jan 19, 2013 at 5:39 PM, Daniel Vetter <<a href="mailto:daniel@ffwll.ch" target="_blank">daniel@ffwll.ch</a>> wrote:<br>
>><br>
>> Hi Jonathan,<br>
>><br>
>> Can you please boot with drm.debug=0xe and then attach the complete<br>
>> dmesg once right after boot, and once after the screen went black?<br>
>><br>
>> Thanks, Daniel<br>
>><br>
>> On Sun, Jan 20, 2013 at 1:38 AM, Jonathan Adamczewski<br>
>> <<a href="mailto:jonathan.adamczewski@gmail.com" target="_blank">jonathan.adamczewski@gmail.com</a>> wrote:<br>
>> > Hardware is a Dell XPS laptop, xorg log reports "Integrated Graphics<br>
>> > Chipset: Intel(R) Sandybridge Mobile (GT2)"<br>
>> ><br>
>> > Running a custom configured 3.7.2 based kernel,<br>
>> > xf86-video-intel-2.20.17.<br>
>> ><br>
>> > I'm running the internal LVDS screen at 1080p and a Dell 2713HM monitor<br>
>> > at<br>
>> > 2560x1440 connected via display port.<br>
>> ><br>
>> > Both screens run fine when X starts, but at some point the external<br>
>> > monitor<br>
>> > will go black. The system doesn't recognize it as being disconnected -<br>
>> > no<br>
>> > KDE popup asking if I want to change the monitor config as happens when<br>
>> > pulling the DP or power on the monitor.<br>
>> ><br>
>> > Sometimes it will return to life after a short amount of time, most of<br>
>> > the<br>
>> > time it stays black indefinitely. A full power cycle of the monitor<br>
>> > (pulling<br>
>> > the plug) will usually bring it back to life, but typically not for<br>
>> > long.<br>
>> ><br>
>> > The screen usually goes black while there's a high degree of display<br>
>> > activity - a video playing, moving large windows around the screen,<br>
>> > looking<br>
>> > around in google streetview, etc. It doesn't seem to matter which screen<br>
>> > the<br>
>> > activity is on.<br>
>> ><br>
>> > It *seems* to be less likely if I run the external display at a lower<br>
>> > resolution.<br>
>> ><br>
>> > There's nothing that coincides with the screen going black in dmesg or<br>
>> > the<br>
>> > xorg log.<br>
>> ><br>
>> > I've had no problems with this monitor under Windows 7 (gaming, videos,<br>
>> > etc).<br>
>> ><br>
>> > What I'm looking for: ideally a simple fix :) Otherwise, any suggestions<br>
>> > about where to look to gather more information on what could be<br>
>> > happening<br>
>> > here - or other places to ask for help.<br>
>> ><br>
>> > Many thanks<br>
>> ><br>
>> > jonathan.<br>
>> ><br>
>> > _______________________________________________<br>
>> > Intel-gfx mailing list<br>
>> > <a href="mailto:Intel-gfx@lists.freedesktop.org" target="_blank">Intel-gfx@lists.freedesktop.org</a><br>
>> > <a href="http://lists.freedesktop.org/mailman/listinfo/intel-gfx" target="_blank">http://lists.freedesktop.org/mailman/listinfo/intel-gfx</a><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> Daniel Vetter<br>
>> Software Engineer, Intel Corporation<br>
>> <a href="tel:%2B41%20%280%29%2079%20365%2057%2048" value="+41793655748" target="_blank">+41 (0) 79 365 57 48</a> - <a href="http://blog.ffwll.ch" target="_blank">http://blog.ffwll.ch</a><br>
><br>
><br>
<br>
<br>
<br>
--<br>
Daniel Vetter<br>
Software Engineer, Intel Corporation<br>
<a href="tel:%2B41%20%280%29%2079%20365%2057%2048" value="+41793655748" target="_blank">+41 (0) 79 365 57 48</a> - <a href="http://blog.ffwll.ch" target="_blank">http://blog.ffwll.ch</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>