From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27868] New: [r600] on new campaign, Vegastrike crashes or freezes Xorg
Date: Wed, 28 Apr 2010 05:39:40 -0700 (PDT) [thread overview]
Message-ID: <bug-27868-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=27868
Summary: [r600] on new campaign, Vegastrike crashes or freezes
Xorg
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=35318)
--> (https://bugs.freedesktop.org/attachment.cgi?id=35318)
Backtrace
While other OpenGL applications are running without problem (extreme-tuxracer,
emilia-pinball, xscreensaver), Vegastrike will either crash or freeze Xorg when
starting a new campaign.
When Xorg freezes it becomes unkillable, with Vegastrike and Xorg at 100% CPU,
and I need to ssh into to restart.
Gentoo Linux, amd64, ATI HD3200 (780G)
xorg-server-1.7.6
x11-libs/libdrm-2.4.18_pre20100211-r1
xf86-video-ati-6.13.0
mesa-7.7.1
vegastrike svn
The same happens with vegastrike-0.5.0.
Backtrace of crash, xorg.conf, Xorg log attached.
--
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-04-28 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 12:39 bugzilla-daemon [this message]
2010-04-28 12:40 ` [Bug 27868] [r600] on new campaign, Vegastrike crashes or freezes Xorg bugzilla-daemon
2010-04-28 12:41 ` bugzilla-daemon
2010-05-05 10:44 ` bugzilla-daemon
2010-05-07 14:26 ` bugzilla-daemon
2010-07-20 14:47 ` bugzilla-daemon
2010-07-20 14:52 ` bugzilla-daemon
2010-08-01 13:49 ` bugzilla-daemon
2010-08-20 9:12 ` 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-27868-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.