On Fri, Jul 05, 2013 at 06:34:46PM -0300, Paulo Zanoni wrote: > 2013/7/4 Daniel Vetter <daniel at ffwll.ch>: > > 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 <chris at chris-wilson.co.uk> > >> Cc: Daniel Vetter <daniel.vetter at ffwll.ch> > > > > Picked up for -fixes, thanks for the patch. Let's see what happens ... > > This happens: > > pzanoni at 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
