From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paulo Zanoni Subject: Re: [Intel-gfx] [git pull] drm merge for 3.9-rc1 Date: Thu, 28 Feb 2013 11:31:45 -0300 Message-ID: References: <20130228111819.GF11892@cantiga.alporthouse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mail-oa0-f43.google.com ([209.85.219.43]:59333 "EHLO mail-oa0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751332Ab3B1Obp (ORCPT ); Thu, 28 Feb 2013 09:31:45 -0500 In-Reply-To: <20130228111819.GF11892@cantiga.alporthouse.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Chris Wilson , Sedat Dilek , Dave Airlie , DRI , intel-gfx , LKML , linux-next Hi 2013/2/28 Chris Wilson : > On Thu, Feb 28, 2013 at 12:06:28AM +0100, Sedat Dilek wrote: >> On Wed, Feb 27, 2013 at 11:36 PM, Sedat Dilek wrote: >> > Hi, >> > >> > I am seeing this also on Linux-Next. >> > >> > /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.202381] >> > [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout >> > (has irq: 1)! >> > /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.210588] >> > [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout >> > (has irq: 1)! >> > >> > /var/log/kern.log.1:Feb 22 07:36:04 fambox kernel: [ 27.408280] >> > [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout >> > (has irq: 1)! >> > >> > This seems to be hard reproducible... >> > Laptop-LCD... Sandybridge Mobile-GT2. >> > >> > Is there a way to force the error? >> > >> > Possible patch see [1]. >> > >> > - Sedat - >> > >> > [1] https://patchwork.kernel.org/patch/2192721/ > > That was: > > + if (!done) { > + status = I915_READ_NOTRACE(ch_ctl); > + DRM_ERROR("dp aux hw did not signal timeout (has irq: > %i), status=%08x!\n", > + has_aux_irq, status); > + } > > You applied > > + if (!done) { > + status = I915_READ_NOTRACE(ch_ctl); > + DRM_ERROR("dp aux hw did not signal timeout (has irq: > %i), status=%08x!\n", > + has_aux_irq, status); > + { In addition to this, after the problem happens can you please dump the registers 0x44008 (DEIIR) and 0xC4008 (SDEIIR)? You can do this either by running intel-reg-read (from intel-gpu-tools) or by changing the DRM_ERROR above to also print the result of I915_READ(0x44008) and I915_READ(0xC4008). If you conclude that the value of 0x44008 is 0x0 while the value of 0xC4008 is not, then this patch should help: https://patchwork.kernel.org/patch/2177841/ > > That second '{' is the source of the compile error. > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Paulo Zanoni