From: Jesse Barnes Subject: Re: FBC underruns on GMA4500? Date: Mon, 9 Aug 2010 10:26:24 -0700 Message-ID: <20100809102624.683e8729@virtuousgeek.org> References: <1281174379.6047.5.camel@zwerg> <20100809093607.01b5013f@virtuousgeek.org> <1281374434.5106.3.camel@zwerg> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from cpoproxy3-pub.bluehost.com (cpoproxy3-pub.bluehost.com [67.222.54.6]) by gabe.freedesktop.org (Postfix) with SMTP id 8F3ED9ECD4 for ; Mon, 9 Aug 2010 10:26:26 -0700 (PDT) In-Reply-To: <1281374434.5106.3.camel@zwerg> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Alexey Fisher Cc: "intel-gfx@lists.freedesktop.org" List-Id: intel-gfx@lists.freedesktop.org On Mon, 09 Aug 2010 19:20:34 +0200 Alexey Fisher wrote: > On Mo, 2010-08-09 at 09:36 -0700, Jesse Barnes wrote: > > On Sat, 07 Aug 2010 11:46:19 +0200 > > Alexey Fisher wrote: > > > > > Hallo all, > > > > > > i have some times on my primer desktop with Intel DG45ID board some sort > > > of flickering, it schort (1 second) and only half of the display. Same > > > sort of flickering i had with Bug 24314 - [945GME FBC] underruns > > > followed by freeze after resume with FBC enabled. The difference is - it > > > will not freeze. > > > > > > If i understand it correctly , it is not normal. But i can't report it, > > > there is no messages in dmesg or xorg.log > > > > Sounds like potential FIFO underruns, maybe your memory configuration > > doesn't match the latency we expect in intel_display.c. You could try > > increasing the latency constant in that file to see if it makes the > > flicker go away. > > Can you please point me what file to change? And haw can i check what > latency is used? drivers/gpu/drm/i915/intel_display.c, modify (increase) the latency_ns variable to say 10000. > > If that helps it's just another example of why we need better latency > > detection in the driver; unfortunately we don't know how to do that > > yet... > > Please take a look to this bug: > https://bugs.freedesktop.org/show_bug.cgi?id=29454 > may be FIFO underrun and hangs have same source. Yeah repeated underruns can lead to chip hangs. -- Jesse Barnes, Intel Open Source Technology Center