From patchwork Sun Jan 20 11:52:05 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Daniel Vetter X-Patchwork-Id: 2008141 Return-Path: X-Original-To: patchwork-intel-gfx@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) by patchwork2.kernel.org (Postfix) with ESMTP id 44EB1DF223 for ; Sun, 20 Jan 2013 11:52:16 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 0B9B9E5FA6 for ; Sun, 20 Jan 2013 03:52:16 -0800 (PST) X-Original-To: intel-gfx@lists.freedesktop.org Delivered-To: intel-gfx@lists.freedesktop.org Received: from mail-bk0-f41.google.com (mail-bk0-f41.google.com [209.85.214.41]) by gabe.freedesktop.org (Postfix) with ESMTP id B4F95E5E69 for ; Sun, 20 Jan 2013 03:52:06 -0800 (PST) Received: by mail-bk0-f41.google.com with SMTP id jg9so2623488bkc.28 for ; Sun, 20 Jan 2013 03:52:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=mime-version:x-received:sender:x-originating-ip:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=+P08OFzbmv1GtfiXcLJRrKYzqlabk8AddQdG4OcCkj8=; b=DFxZ95ZZM8yEFZsaBZQq+T6unpgD/Zl79Awv2EtFeSRJtPGjzeOs09c79qfHw/Y/GE cxwnRvB4ruUN0dBUDlPIyzA7k/jPCJluCHipt0ZCDbhtuTfnovzr9kCdzxswmQ8OHn3V dK8C6YWaDDH5/nZgOngX1hMPUY44ILVBLMEzE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:x-originating-ip:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:x-gm-message-state; bh=+P08OFzbmv1GtfiXcLJRrKYzqlabk8AddQdG4OcCkj8=; b=nyBMbbIsGcBwcNvWJ152KH5nM08VTkM90ZHRh20efL2hodAscaz1KQ6jzZHMdycu8f 0A+sN1b6Y1YtrahpuHT/ttCXMacq/FLsTjWZApEzi6TgqLgPC652kdMT04RnWbRZVxRi IBQebsyiV1qXj3lBwQVPkpBGQoLXAX6toMaupN6wpYVjiZTCh/Ttq5IxvtnPUueiD5KQ H00t0vuN/PoBjqS1yPvUT7Pn4fHmjWJqpTzWpA5Ofe5jWRJ6p0vZwaaDSENJ6EGvb6Wt OxqyU03S6zo5vMx0pTEJdN7JhCiwjo5zz3Rk3cq5I2+zt/aykr0I8Ymkv/bdDjJRE/w0 z/Zw== MIME-Version: 1.0 X-Received: by 10.204.12.220 with SMTP id y28mr4142232bky.112.1358682725524; Sun, 20 Jan 2013 03:52:05 -0800 (PST) Received: by 10.204.35.136 with HTTP; Sun, 20 Jan 2013 03:52:05 -0800 (PST) X-Originating-IP: [178.83.130.250] In-Reply-To: References: Date: Sun, 20 Jan 2013 12:52:05 +0100 X-Google-Sender-Auth: JeDbojB6gcJ38zfuhzzKkIjtI2M Message-ID: From: Daniel Vetter To: Jonathan Adamczewski X-Gm-Message-State: ALoCoQnOqS3SV/xI0qsosdbw0v5L+B1pPE+U55VdYY2Ry55Q//fVO84rFqCiLEJ3LafE3gJzfHIA Cc: intel-gfx@lists.freedesktop.org Subject: Re: [Intel-gfx] external screen goes black X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+patchwork-intel-gfx=patchwork.kernel.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+patchwork-intel-gfx=patchwork.kernel.org@lists.freedesktop.org Hm, it's a DP screen which I've suspected (those are the kind who can lose sync and go black). But somehow we don't get any hotplug event when this happens - so the driver has no idea that the link went bad and that we need to retrain. Can you please test this with this snippet: Also please check whether yanking and re-plugging the DP cable will restore the display - it should. -Daniel On Sun, Jan 20, 2013 at 5:45 AM, Jonathan Adamczewski wrote: > Thanks for the reply, Daniel. > > Full traces are attached. I booted the system, ran dmesg after logging in > through kdm. > > (Then I left the system while doing some other errands, hence the gap in > time) > > I then started firefox, went to youtube and started watching some 4K > resolution videos. The external screen went black in less than a minute. > Second file is dmesg run after that - there doesn't appear to be much to > see... > > There was nothing in dmesg that correlated directly with the screen going > black. I've validated this by triggering the screen going black several > times (that's not in the attached log, though) - there was never anything in > dmesg that happened at the same time or that happened for tens of seconds > thereafter. > > > What's the next step for gathering information here? > > Many thanks > > Jonathan. > > > > > > On Sat, Jan 19, 2013 at 5:39 PM, Daniel Vetter wrote: >> >> Hi Jonathan, >> >> Can you please boot with drm.debug=0xe and then attach the complete >> dmesg once right after boot, and once after the screen went black? >> >> Thanks, Daniel >> >> On Sun, Jan 20, 2013 at 1:38 AM, Jonathan Adamczewski >> wrote: >> > Hardware is a Dell XPS laptop, xorg log reports "Integrated Graphics >> > Chipset: Intel(R) Sandybridge Mobile (GT2)" >> > >> > Running a custom configured 3.7.2 based kernel, >> > xf86-video-intel-2.20.17. >> > >> > I'm running the internal LVDS screen at 1080p and a Dell 2713HM monitor >> > at >> > 2560x1440 connected via display port. >> > >> > Both screens run fine when X starts, but at some point the external >> > monitor >> > will go black. The system doesn't recognize it as being disconnected - >> > no >> > KDE popup asking if I want to change the monitor config as happens when >> > pulling the DP or power on the monitor. >> > >> > Sometimes it will return to life after a short amount of time, most of >> > the >> > time it stays black indefinitely. A full power cycle of the monitor >> > (pulling >> > the plug) will usually bring it back to life, but typically not for >> > long. >> > >> > The screen usually goes black while there's a high degree of display >> > activity - a video playing, moving large windows around the screen, >> > looking >> > around in google streetview, etc. It doesn't seem to matter which screen >> > the >> > activity is on. >> > >> > It *seems* to be less likely if I run the external display at a lower >> > resolution. >> > >> > There's nothing that coincides with the screen going black in dmesg or >> > the >> > xorg log. >> > >> > I've had no problems with this monitor under Windows 7 (gaming, videos, >> > etc). >> > >> > What I'm looking for: ideally a simple fix :) Otherwise, any suggestions >> > about where to look to gather more information on what could be >> > happening >> > here - or other places to ask for help. >> > >> > Many thanks >> > >> > jonathan. >> > >> > _______________________________________________ >> > Intel-gfx mailing list >> > Intel-gfx@lists.freedesktop.org >> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx >> > >> >> >> >> -- >> Daniel Vetter >> Software Engineer, Intel Corporation >> +41 (0) 79 365 57 48 - http://blog.ffwll.ch > > diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c index 1492706..5e91242 100644 --- a/drivers/gpu/drm/i915/intel_dp.c +++ b/drivers/gpu/drm/i915/intel_dp.c @@ -2580,6 +2580,8 @@ intel_dp_hot_plug(struct intel_encoder *intel_encoder) { struct intel_dp *intel_dp = enc_to_intel_dp(&intel_encoder->base); + printk("hotplug interrupt for DP\n"); + intel_dp_check_link_status(intel_dp); }