<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - R6xx freezes with kernel 3.17 and up"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91268#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - R6xx freezes with kernel 3.17 and up"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91268">bug 91268</a>
from <span class="vcard"><a class="email" href="mailto:kap3tan@gmail.com" title="Kajzer <kap3tan@gmail.com>"> <span class="fn">Kajzer</span></a>
</span></b>
<pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=91268#c9">comment #9</a>)
<span class="quote">> That's expected. Alex's patch isn't a fix but just to confirm the problem is
> really directly related to write-combined CPU mappings.</span >
Yeah I know, that's what I really asked for, a way to disable that commit.
I can confirm now that indeed there's some bug in that commit (with R6xx chips)
I had no hangs with mappings disabled.
I'm willing to test potential fixes.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>