From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64320] WebGL support in Chrome causes GPU lockup
Date: Tue, 07 May 2013 14:59:14 +0000 [thread overview]
Message-ID: <bug-64320-502-M0f7rWVMFY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64320-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 559 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=64320
--- Comment #3 from Marc Dietrich <marvin24@gmx.de> ---
I don't see Kwin corruptions as reported in bug 64257. Also this bug says
nothing about GPU lockups. But what I also see is a "dark glxgears" effect.
It's kinda hard to bisect this because r600 now depends on llvm and different
mesa versions may require different llvm versions. I can try using the llvm
version as written in LLVM_REVISION.TXT, but that may take some time.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1466 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-07 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 13:38 [Bug 64320] New: WebGL support in Chrome causes GPU lockup bugzilla-daemon
2013-05-07 14:17 ` [Bug 64320] " bugzilla-daemon
2013-05-07 14:25 ` bugzilla-daemon
2013-05-07 14:59 ` bugzilla-daemon [this message]
2013-05-07 15:01 ` [Bug 64320] WebGL support in Chrome causes GPU lockup when using llvm bugzilla-daemon
2013-05-14 15:04 ` bugzilla-daemon
2013-05-14 17:10 ` bugzilla-daemon
2013-05-14 17:11 ` 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-64320-502-M0f7rWVMFY@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