From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Verify that our stolen memory doesn't conflict
Date: Fri, 5 Jul 2013 23:39:33 +0200 [thread overview]
Message-ID: <20130705213933.GA18285@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGT2MCCYtSa482PZat0tArSBZ18f8sYFjZHLPs7OnEgqhQ@mail.gmail.com>
On Fri, Jul 05, 2013 at 06:34:46PM -0300, Paulo Zanoni wrote:
> 2013/7/4 Daniel Vetter <daniel@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@chris-wilson.co.uk>
> >> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> >
> > 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
next prev parent reply other threads:[~2013-07-05 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 23:23 [PATCH] drm/i915: Use Graphics Base of Stolen Memory on all gen3+ Chris Wilson
2013-07-03 23:26 ` Daniel Vetter
2013-07-03 23:33 ` Chris Wilson
2013-07-03 23:38 ` Daniel Vetter
2013-07-03 23:55 ` Chris Wilson
2013-07-04 9:55 ` Daniel Vetter
2013-07-04 10:53 ` [PATCH] drm/i915: Verify that our stolen memory doesn't conflict Chris Wilson
2013-07-04 11:05 ` Daniel Vetter
2013-07-04 11:28 ` Chris Wilson
2013-07-04 12:44 ` Daniel Vetter
2013-07-05 21:34 ` Paulo Zanoni
2013-07-05 21:39 ` Daniel Vetter [this message]
2013-07-23 17:30 ` [PATCH] drm/i915: Use Graphics Base of Stolen Memory on all gen3+ Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130705213933.GA18285@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=przanoni@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox