Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759073Ab3HMULh (ORCPT ); Tue, 13 Aug 2013 16:11:37 -0400 Received: from s16502780.onlinehome-server.info ([87.106.93.118]:50386 "EHLO fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1759024Ab3HMULf (ORCPT ); Tue, 13 Aug 2013 16:11:35 -0400 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.73.22; Date: Tue, 13 Aug 2013 21:10:42 +0100 From: Chris Wilson To: Sedat Dilek Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Daniel Vetter , Dave Airlie , DRI , intel-gfx , "s.dilek" Subject: Re: linux-next: Tree for Aug 13 [ screen corruption in graphical mode ] Message-ID: <20130813201042.GA6390@cantiga.alporthouse.com> Mail-Followup-To: Chris Wilson , Sedat Dilek , Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Daniel Vetter , Dave Airlie , DRI , intel-gfx , "s.dilek" References: <20130813163439.GA8805@cantiga.alporthouse.com> <20130813171324.GB8805@cantiga.alporthouse.com> <20130813180129.GC8805@cantiga.alporthouse.com> <20130813185322.GA5982@cantiga.alporthouse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Originating-IP: 78.156.73.22 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2233 Lines: 55 On Tue, Aug 13, 2013 at 09:05:41PM +0200, Sedat Dilek wrote: > On Tue, Aug 13, 2013 at 8:53 PM, Chris Wilson wrote: > > On Tue, Aug 13, 2013 at 08:40:37PM +0200, Sedat Dilek wrote: > >> On Tue, Aug 13, 2013 at 8:01 PM, Chris Wilson wrote: > >> > On Tue, Aug 13, 2013 at 07:53:25PM +0200, Sedat Dilek wrote: > >> >> Files attached. > >> > > >> > Can you also please attach a full dmesg so I can check for anything > >> > unusual? > >> > > > > > Nothing scarred me on a couple of read throughs. > > > > What happens if you try: > > > > diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c b/drivers/gpu/drm/i915/i915_gem_stolen.c > > index 112c5e1..9828d9b 100644 > > --- a/drivers/gpu/drm/i915/i915_gem_stolen.c > > +++ b/drivers/gpu/drm/i915/i915_gem_stolen.c > > @@ -284,7 +284,7 @@ i915_gem_object_create_stolen(struct drm_device *dev, u32 size) > > return NULL; > > > > ret = drm_mm_insert_node(&dev_priv->mm.stolen, stolen, size, > > - 4096, DRM_MM_SEARCH_DEFAULT); > > + 1024*1024, DRM_MM_SEARCH_DEFAULT); > > if (ret) { > > kfree(stolen); > > return NULL; > > > > -- > > Now, 2/3 till 3/4 of my LightDM greeter screen is a black bar (seen > from the top). > On the bottom I can read "Ubuntu 12.04 LTS" with the known background. > So-to-say 3/4 "blind". That implies that the scanout is always reading from the base of stolen. Can you grab intel_reg_dumper so that I can check what values the transcoder is set to? At the moment, I am guessing that the display never sees the updated surface offset and so persists with the value programmed by the BIOS - which will be 0 and set to the base of stolen memory in the GTT. A drm.debug=6 dmesg would help here as well. If you forced a mode change, I think that too would restore the output. -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/