From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29680] New: [r600g] oolite segfaults on initialization
Date: Thu, 19 Aug 2010 12:21:52 -0700 (PDT) [thread overview]
Message-ID: <bug-29680-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29680
Summary: [r600g] oolite segfaults on initialization
Product: Mesa
Version: unspecified
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=37992)
--> (https://bugs.freedesktop.org/attachment.cgi?id=37992)
backtrace
KMS r600 gallium:
With mesa-git (plus color field patch set by Luca Barbieri, for bug 29644),
Oolite-1.74.2 segfaults during initialization.
It's working nicely with KMS r600 classic.
Right before crashing I see these errors:
EE r600_shader.c/tgsi_unsupported:537 - 30 tgsi opcode unsupported
EE r600_shader.c/r600_pipe_shader_create:115 - translation from TGSI failed !
EE r600_shader.c/tgsi_unsupported:537 - 31 tgsi opcode unsupported
EE r600_shader.c/r600_pipe_shader_create:115 - translation from TGSI failed !
System environment:
-- system architecture: amd64
-- Linux distribution: Gentoo
-- GPU: RS780G
-- Model: ATI Radeon HD 3200
-- Display connector: VGA
-- xf86-video-ati: cc0a167ff2db9b097891883ded147af1d67e4407
-- xserver: 1.8.2
-- mesa: c54dea66fd86f6000e334c703ea4890179c39c81
(+ patch set by Luca Barbieri, for bug 29644)
-- drm: 431f7f00db844534dbcf9a63da0d2832a3d91bff
-- kernel: 2.6.35.1
--
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-08-19 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 19:21 bugzilla-daemon [this message]
2010-08-23 13:17 ` [Bug 29680] [r600g] oolite segfaults on initialization 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-29680-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