From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: [PATCH] drm/i915: Verify that our stolen memory doesn't conflict Date: Fri, 5 Jul 2013 23:39:33 +0200 Message-ID: <20130705213933.GA18285@phenom.ffwll.local> References: <1372937315-17046-1-git-send-email-chris@chris-wilson.co.uk> <20130704124423.GF18285@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-ee0-f51.google.com (mail-ee0-f51.google.com [74.125.83.51]) by gabe.freedesktop.org (Postfix) with ESMTP id 24BDBE602F for ; Fri, 5 Jul 2013 14:39:34 -0700 (PDT) Received: by mail-ee0-f51.google.com with SMTP id e52so1594782eek.38 for ; Fri, 05 Jul 2013 14:39:34 -0700 (PDT) Content-Disposition: inline In-Reply-To: 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: Paulo Zanoni Cc: Daniel Vetter , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Fri, Jul 05, 2013 at 06:34:46PM -0300, Paulo Zanoni wrote: > 2013/7/4 Daniel Vetter : > > On Thu, Jul 04, 2013 at 12:28:35PM +0100, Chris Wilson wrote: > >> Sanity check that the memory region found through the Graphics Base > >> of Stolen Memory is reserved and hidden from the rest of the system > >> through the use of the resource API. > >> > >> v2: "Graphics Stolen Memory" is such a more bodacious name than the lame > >> "i915 stolen", and convert to using devres for automagical cleanup of > >> the resource. (danvet) > >> > >> Signed-off-by: Chris Wilson > >> Cc: Daniel Vetter > > > > Picked up for -fixes, thanks for the patch. Let's see what happens ... > > This happens: > > pzanoni@sopa:~$ dmesg | grep stolen > [ 2.025951] [drm:i915_gem_gtt_init], GTT stolen size = 128M > [ 2.059755] [drm:i915_stolen_to_physical] *ERROR* conflict detected > with stolen region: [2812280832 - 2946498560] > > As a consequence, FBC refuses to load. I'm not sure if this is a > bug... Is this expected? Is there any way I can help debug this? I guess we need the e820 map from dmesg and compare which part is blocking the stolen range ... Can you please attach your full dmesg? -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch