From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40667] New: Radeon 6850 Segmentation Fault - ARB_vertex_type_2_10_10_10_rev
Date: Tue, 6 Sep 2011 21:38:37 -0700 (PDT) [thread overview]
Message-ID: <bug-40667-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=40667
Summary: Radeon 6850 Segmentation Fault -
ARB_vertex_type_2_10_10_10_rev
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: spamjunkeater@gmail.com
My HD6850 started to give segmentation fault with glxinfo (also with others)
with this commit.
Don't know why. Found by git bisect....
Thanks
death@triQuad:/media/ext4/gallium> git bisect bad
3543160f56f1f966587e07b1620496c8fe5be325 is the first bad commit
commit 3543160f56f1f966587e07b1620496c8fe5be325
Author: Dave Airlie <airlied@redhat.com>
Date: Mon Nov 22 08:11:46 2010 +1000
glapi: add ARB_vertex_type_2_10_10_10_rev entrypoints. (v2)
These are the new API entrypoints for ARB_vertex_type_2_10_10_10_rev
extension, along with the new INT_2_10_10_10_REV enum.
v2: fixup crazy whitespace cut-n-paste mess
Signed-off-by: Dave Airlie <airlied@redhat.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
:040000 040000 018dba6214a3f4bd39dda6a4d9c75d20fcd09ba0
9d6b27f1d3264100006ebea047d5cd9d2aa84c36 M src
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-09-07 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 4:38 bugzilla-daemon [this message]
2011-09-07 4:45 ` [Bug 40667] Radeon 6850 Segmentation Fault - ARB_vertex_type_2_10_10_10_rev bugzilla-daemon
2011-09-07 5:02 ` bugzilla-daemon
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=bug-40667-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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.