gen6 (SNB) depthbuffer issue with OpenGL games
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.
Any Clues?
Regards
Nic
-----Ursprüngliche Nachricht-----
Von: "Nicolas Kalkhof" <[email protected]>
Gesendet: Jul 19, 2011 9:08:26 PM
An: "Ian Romanick" <[email protected]>
Betreff: Re: [Intel-gfx] gen6 (SNB) depthbuffer issue with OpenGL games
Quoted 41 lines
Hi Ian,
thx for your reply. ok I give it a try and will report my findings....
regards
nic-----Ursprüngliche Nachricht-----
Von: "Ian Romanick" <[email protected]>
Gesendet: Jul 19, 2011 8:45:53 PM
An: "Nicolas Kalkhof" <[email protected]>
Betreff: Re: [Intel-gfx] gen6 (SNB) depthbuffer issue with OpenGL gamesQuoted 22 lines
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 8 lines · Nicolas Kalkhof
Hi there,
I've experienced a strange depth buffer issue recently with OpenGL games (see attached screenshots). It seems that the depth buffer fails on some pixels. This problem was introduced somewhere between Kernel-3.0.0-rc6-git6 and kernel-3.0.0-rc7. Both xf-86-video-intel and mesa are latest git.
Could someone please look into it?That's very odd. Any chance you could bisect to find the bad commit? You should be able to just bisect the
drivers/gpu/drmdirectory. I'm a bit suspicious that this is a kernel issue. There were only 5 commits indrivers/gpu/drmfrom rc6 to rc7, and none of them should affect any Intel GPUs at all.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/Quoted 4 lines
iEYEARECAAYFAk4l0OEACgkQX1gOwKyEAw/BWQCfeySgLPcT1bdNxPcTJr/S2aw0 vvkAnjS5OJF18pRwrRKaMyG2zoXFqwqB
=AiSG
-----END PGP SIGNATURE-----
Quoted 7 lines
___________________________________________________________
Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar
_______________________________________________
Intel-gfx mailing list [email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
___________________________________________________________
Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar
_______________________________________________
Intel-gfx mailing list [email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Netiquette (was: gen6 (SNB) depthbuffer issue with OpenGL games)
Dear Nicolas,
unfortunately the Web.de WWW interface has stopped to set the In-Reply-To or References header fields in the message header and therefore does not adhere to the standard anymore [1]. As a result your messages are not threaded correctly which make keeping an overview harder [2].
Do you have the means to use a mail program like Evolution, Thunderbird, etc. which adhere to the standard? Web.de Freemail supports IMAP so that you could still manage your mail on the server.
As a last thing, could you also try to use interleaved style when replying. Doing this is also easier when using mail programs in my experience.
Thanks,
Paul
[1] http://lists.alioth.debian.org/pipermail/pkg-exim4-users/2011-June/001949.html
[2] http://en.opensuse.org/openSUSE:Mailing_list_netiquette
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Ian Romanick
Tested-by Lin Ming-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 8 lines · Nicolas Kalkhof
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.care the cause of the problem.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 <[email protected]> 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
-----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-----