From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29996] New: r600g, bisected: oolite segfaults on init with assertion failure
Date: Fri, 3 Sep 2010 05:26:50 -0700 (PDT) [thread overview]
Message-ID: <bug-29996-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29996
Summary: r600g, bisected: oolite segfaults on init with
assertion failure
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: nikai@nikai.net
Created an attachment (id=38401)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38401)
backtrace
On initialisation, oolite-1.74.2 segfaults with an assertion failure.
Only with r600 Gallium driver, working nicely with r600 Classic.
Bisected to mesa: ce7077423fc9ea003606dd28ca87311644b7e5c2
(Dave Airlie, r600g: deref old driver states for set entry points.)
../../../../src/gallium/auxiliary/util/u_inlines.h:87:pipe_reference_described:
Assertion `pipe_is_referenced(ptr)' failed.
System environment:
-- system architecture: amd64
-- Linux distribution: Gentoo
-- GPU: RS780G
-- Model: ATI Radeon HD 3200
-- Display connector: VGA
-- xf86-video-ati: 2b98ec1f7e931019a4ab699a56d5dfaa395946fb
-- xserver: 1.9.0
-- mesa: 50c1b6f2e845c067ac91493c0f93caca794521dd
-- drm: 8a76244a0fd09d0e3298fe68af812d7eaa4dbcb5
-- kernel: 2.6.35.3
--
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:[~2010-09-03 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 12:26 bugzilla-daemon [this message]
2010-09-06 12:13 ` [Bug 29996] r600g, bisected: oolite segfaults on init with assertion failure 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-29996-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox