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: Sun, 24 Aug 2014 01:05:04 +0000 [thread overview]
Message-ID: <bug-78221-2300-Ut3qpdFdks@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-78221-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=78221
--- Comment #18 from t3st3r@mail.ru ---
This is getting even more interesting. After some investigation I got idea why
bisect never succeeds. It looks like there was no stable kernels at all: 3.15
is also broken. However it takes "almost forever" to crash it with previously
used methods.
Somehow I stepped up on similar but far more optimized use case (another map in
BfW game) which locks up GPU in matter of seconds to a minute. That's what I
need :). This also proven to knock down "good" 3.15 kernels in matter of 30
seconds or so. So it was not good at all. Obviously my bisect can't succeed.
On other hand now I can try mentioned patches...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-24 1:05 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 [this message]
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
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-Ut3qpdFdks@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).