From: Ian Romanick <idr@freedesktop.org>
To: Nicolas Kalkhof <nkalkhof@web.de>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: gen6 (SNB) depthbuffer issue with OpenGL games
Date: Tue, 19 Jul 2011 14:08:14 -0700 [thread overview]
Message-ID: <4E25F23E.30509@freedesktop.org> (raw)
In-Reply-To: <1462919164.9316293.1311106886755.JavaMail.fmail@mwmweb010>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/19/2011 01:21 PM, Nicolas Kalkhof wrote:
> Hi all,
>
> ok I've nailed the issue down to 3.0.0-rc7 and 3.0.0-rc7-git1. I suspect that the changes made in
> drivers/gpu/drm/i915/i915_dma.c are the cause of the problem.
>
> http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv3.0%2Fsnapshots%2Fpatch-3.0-rc7-git1.bz2;z=14
>
> Any Clues?
Okay, so that's the commit below, which changes some error clean-up
paths. That is also odd. What *exact* GPU do you have? Specificially,
what's the output of
glxinfo | grep "OpenGL renderer"
and
lspci -vn | grep VGA
Does this appear in all games or just certain games? If it's just in
certain games, which ones?
commit a7b85d2aa63ed09cd5a4a640772b3272f5ac7caa
Author: Keith Packard <keithp@keithp.com>
Date: Sun Jul 10 13:12:17 2011 -0700
drm/i915: Clean up i915_driver_load failure path
i915_driver_load adds a write-combining MTRR region for the GTT
aperture to improve memory speeds through the aperture. If
i915_driver_load fails after this, it would not have cleaned up the
MTRR. This shouldn't cause any problems, except for consuming an MTRR
register. Still, it's best to clean up completely in the failure path,
which is easily done by calling mtrr_del if the mtrr was successfully
allocated.
i915_driver_load calls i915_gem_load which register
i915_gem_inactive_shrink. If i915_driver_load fails after calling
i915_gem_load, the shrinker will be left registered. When called, it
will access freed memory and crash. The fix is to unregister the
shrinker in the
failure path using code duplicated from i915_driver_unload.
i915_driver_load also has some incorrect gotos in the error cleanup
paths:
* After failing to initialize the GTT (which cannot happen, btw,
intel_gtt_get returns a fixed (non-NULL) value), it tries to
free the uninitialized WC IO mapping. Fixed this by changing the
target from out_iomapfree to out_rmmap
Signed-off-by: Keith Packard <keithp@keithp.com>
Tested-by: Lin Ming <ming.m.lin@intel.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk4l8j4ACgkQX1gOwKyEAw+XRACaAzuKEihGpktWtA0UbTwx78NR
kBEAoJ7FxkXWEtxC5enkFwnFc19+sPGT
=abq+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-07-19 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 20:21 gen6 (SNB) depthbuffer issue with OpenGL games Nicolas Kalkhof
2011-07-19 20:40 ` Netiquette (was: gen6 (SNB) depthbuffer issue with OpenGL games) Paul Menzel
2011-07-19 21:08 ` Ian Romanick [this message]
[not found] <1234514154.1327484.1311150269401.JavaMail.fmail@mwmweb022>
2011-07-20 14:50 ` gen6 (SNB) depthbuffer issue with OpenGL games Ian Romanick
-- strict thread matches above, loose matches on Subject: below --
2011-07-19 19:18 Nicolas Kalkhof
2011-07-19 18:17 ` Safety0ff
2011-07-19 19:08 Nicolas Kalkhof
[not found] <mailman.27.1311087536.28227.intel-gfx@lists.freedesktop.org>
2011-07-19 15:12 ` Safety0ff
2011-07-19 14:58 Nicolas Kalkhof
2011-07-19 18:45 ` Ian Romanick
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=4E25F23E.30509@freedesktop.org \
--to=idr@freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nkalkhof@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.