From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73083] Semi-repeatable SIGBUS in R600UploadToScreenCS's memcpy
Date: Sun, 29 Dec 2013 13:22:44 +0000 [thread overview]
Message-ID: <bug-73083-502-HTRMburXkR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73083-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 736 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73083
--- Comment #4 from François Guerraz <kubrick@fgv6.net> ---
Created attachment 91287
--> https://bugs.freedesktop.org/attachment.cgi?id=91287&action=edit
Workaround for the evergreen driver
A similar patch for the evergreen family. The bug was reproducible 100% of the
time in my case (by uploading a bunch of pictures using the image uploader on
photobox.com using Firefox 26) and that fixes / work around the problem. It's
hard to tell if there is any performance impact because it used to be crashing.
But using the aforementioned uploader now trigger high (>50%) CPU usage for
Xorg.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1790 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-12-29 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 20:22 [Bug 73083] New: Semi-repeatable SIGBUS in R600UploadToScreenCS's memcpy bugzilla-daemon
2013-12-27 23:50 ` [Bug 73083] " bugzilla-daemon
2013-12-28 0:21 ` bugzilla-daemon
2013-12-29 12:54 ` bugzilla-daemon
2013-12-29 13:22 ` bugzilla-daemon [this message]
2014-01-06 9:32 ` bugzilla-daemon
2014-01-06 9:35 ` 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-73083-502-HTRMburXkR@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).