From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29754] New: [r300g, glsl] Heroes of Newerth lockup GPU
Date: Mon, 23 Aug 2010 09:13:39 -0700 (PDT) [thread overview]
Message-ID: <bug-29754-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29754
Summary: [r300g, glsl] Heroes of Newerth lockup GPU
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: drakkk@centrum.cz
Created an attachment (id=38099)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38099)
dmesg
With latest mesa git when starting HoN it lockup my GPU. This behavior was
introduced with glsl2 merge.
radeon: The kernel rejected CS, see dmesg for more information.
this is printed into terminal many times, no more helpful info, dmesg attached.
To reproduce this just download the game and run it. It isn't free but it
doesn't matter since you won't get as far as the login screen.
BTW I'm not sure if the component should be mesa core or Drivers/DRI/r300, feel
free to change it if it is wrong.
My system:
Kernel: 2.6.35
mesa: c907b947130c884de09e48e1ecbeecc9afc9f75b
GPU: rv530
--
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-23 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 16:13 bugzilla-daemon [this message]
2010-08-23 16:15 ` [Bug 29754] [r300g, glsl] Heroes of Newerth lockup GPU bugzilla-daemon
2010-08-28 4:25 ` bugzilla-daemon
2010-08-28 12:07 ` bugzilla-daemon
2010-09-03 21:09 ` 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-29754-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.