From: Ian Romanick <idr@freedesktop.org>
To: Nicolas Kalkhof <nkalkhof@web.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: gen6 (SNB) depthbuffer issue with OpenGL games
Date: Tue, 19 Jul 2011 11:45:53 -0700 [thread overview]
Message-ID: <4E25D0E1.9050601@freedesktop.org> (raw)
In-Reply-To: <2025156323.8585806.1311087530390.JavaMail.fmail@mwmweb014>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/19/2011 07:58 AM, Nicolas Kalkhof wrote:
> 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/drm directory. I'm a
bit suspicious that this is a kernel issue. There were only 5 commits
in drivers/gpu/drm from 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/
iEYEARECAAYFAk4l0OEACgkQX1gOwKyEAw/BWQCfeySgLPcT1bdNxPcTJr/S2aw0
vvkAnjS5OJF18pRwrRKaMyG2zoXFqwqB
=AiSG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-07-19 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 14:58 gen6 (SNB) depthbuffer issue with OpenGL games Nicolas Kalkhof
2011-07-19 18:45 ` Ian Romanick [this message]
[not found] <mailman.27.1311087536.28227.intel-gfx@lists.freedesktop.org>
2011-07-19 15:12 ` Safety0ff
-- strict thread matches above, loose matches on Subject: below --
2011-07-19 19:08 Nicolas Kalkhof
2011-07-19 19:18 Nicolas Kalkhof
2011-07-19 18:17 ` Safety0ff
2011-07-19 20:21 Nicolas Kalkhof
2011-07-19 21:08 ` Ian Romanick
[not found] <1234514154.1327484.1311150269401.JavaMail.fmail@mwmweb022>
2011-07-20 14:50 ` 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=4E25D0E1.9050601@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.