From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 61533] [r600g][lockup] kernel 3.8/3.9 caused by Opera browser hardware accelerated rendering
Date: Thu, 16 May 2013 12:38:21 +0000 [thread overview]
Message-ID: <bug-61533-502-MH5EL1E4YX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-61533-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 972 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=61533
Alex Deucher <agd5f@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|DRI |Mesa
Version|XFree86 4.4.0 |git
Component|DRM/Radeon |Drivers/Gallium/r600
--- Comment #8 from Alex Deucher <agd5f@yahoo.com> ---
This is most likely a mesa issue; there are several new features in mesa that
are only enabled with a 3.8 kernel. Can one of you use git to bisect mesa to
see what commit broke things? bisecting is a feature of git that allows you to
easily narrow down what commit to a project caused the breakage. You might
also try mesa from the 9.1 branch. Also, if you are using the llvm backend in
the r600 driver, you might try disabling that.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2587 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-05-16 12:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 23:19 [Bug 61533] New: GPU lockups uccurs regularilly on kernel 3.8 caused by Opera browser hardware accelerated rendering bugzilla-daemon
2013-02-26 23:20 ` [Bug 61533] " bugzilla-daemon
2013-02-26 23:21 ` bugzilla-daemon
2013-02-26 23:44 ` bugzilla-daemon
2013-02-26 23:46 ` bugzilla-daemon
2013-03-02 13:57 ` bugzilla-daemon
2013-03-02 19:10 ` bugzilla-daemon
2013-03-02 19:38 ` bugzilla-daemon
2013-04-24 18:51 ` [Bug 61533] [r600g][lockup] " bugzilla-daemon
2013-05-15 22:17 ` bugzilla-daemon
2013-05-16 11:54 ` [Bug 61533] [r600g][lockup] kernel 3.8/3.9 " bugzilla-daemon
2013-05-16 12:38 ` bugzilla-daemon [this message]
2013-05-16 13:39 ` bugzilla-daemon
2013-05-24 18:01 ` bugzilla-daemon
2013-10-07 20:12 ` bugzilla-daemon
2013-10-07 20:14 ` [Bug 61533] [r600g][lockup] kernel 3.8-3.12 " bugzilla-daemon
2014-03-15 12:34 ` bugzilla-daemon
2014-05-13 16:53 ` bugzilla-daemon
2014-05-13 16:58 ` bugzilla-daemon
2014-05-19 11:14 ` bugzilla-daemon
2014-12-04 19:57 ` 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-61533-502-MH5EL1E4YX@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;
as well as URLs for NNTP newsgroup(s).