From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 78221] 3.16 RC1: AMD R9 270 GPU locks up on some heavy 2D activity - GPU VM fault occurs. (possibly DMA copying issue strikes back?)
Date: Fri, 10 Jul 2015 23:38:39 +0000 [thread overview]
Message-ID: <bug-78221-2300-R0ejWNuSld@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-78221-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=78221
Linux Tester <linux.tester@sharklasers.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linux.tester@sharklasers.co
| |m
--- Comment #24 from Linux Tester <linux.tester@sharklasers.com> ---
After some updates to MESA and kernel this bug no longer happens at all - 2D
now rock solid for me on R9 270 and I can run even most troublesome workloads
for weeks without any issues. While I failed to pinpoint what exactly has fixed
bug, thanks anyway. I think it is now safe to close this bug as fixed. I bet
you've got dozens of other GPU lockups to chew on, so I'm glad to inform you at
least one nasty thing has been nailed down.
(it's me, original bug reporter who has forgot password on both original
mailbox and bugzilla account, dammit)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-07-10 23:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 2:20 [Bug 78221] New: 3.16 RC1: AMD R9 270 GPU locks up on some heavy 2D activity - GPU VM fault occurs. (possibly DMA copying issue strikes back?) bugzilla-daemon
2014-06-18 2:22 ` [Bug 78221] " bugzilla-daemon
2014-06-18 15:12 ` bugzilla-daemon
2014-06-19 7:37 ` bugzilla-daemon
2014-06-19 13:46 ` bugzilla-daemon
2014-06-21 4:04 ` bugzilla-daemon
2014-06-22 7:12 ` bugzilla-daemon
2014-06-23 14:44 ` bugzilla-daemon
2014-06-23 14:45 ` bugzilla-daemon
2014-06-24 11:40 ` bugzilla-daemon
2014-06-24 16:23 ` bugzilla-daemon
2014-06-24 16:23 ` bugzilla-daemon
2014-06-25 1:05 ` bugzilla-daemon
2014-06-25 2:11 ` bugzilla-daemon
2014-06-25 9:45 ` bugzilla-daemon
2014-06-25 13:17 ` bugzilla-daemon
2014-08-05 8:06 ` bugzilla-daemon
2014-08-14 11:56 ` bugzilla-daemon
2014-08-24 1:05 ` bugzilla-daemon
2014-08-25 9:58 ` bugzilla-daemon
2014-09-08 12:19 ` bugzilla-daemon
2014-09-08 12:22 ` bugzilla-daemon
2014-09-09 3:09 ` bugzilla-daemon
2014-09-30 4:03 ` bugzilla-daemon
2015-07-10 23:38 ` bugzilla-daemon [this message]
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-78221-2300-R0ejWNuSld@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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).