<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - drm-next-2018-12-14 -Linux PPC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109345#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - drm-next-2018-12-14 -Linux PPC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109345">bug 109345</a>
from <span class="vcard"><a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to Christian Zigotzky from <a href="show_bug.cgi?id=109345#c17">comment #17</a>)
<span class="quote">> (In reply to Alex Deucher from <a href="show_bug.cgi?id=109345#c4">comment #4</a>)
> > Hardly anything in the radeon driver has changed in the last few years.
> > You'd really need to bisect. Also, can you attach a full dmesg (full logs
> > not just filtered for radeon or drm) output from the failed and working
> > cases?
>
> I have found some Radeon changes in these DRM updates:
>
> -rw-r--r-- drivers/gpu/drm/radeon/r300.c 4
> -rw-r--r-- drivers/gpu/drm/radeon/r420.c 1
> -rw-r--r-- drivers/gpu/drm/radeon/radeon.h 3
> -rw-r--r-- drivers/gpu/drm/radeon/radeon_cs.c 4
> -rw-r--r-- drivers/gpu/drm/radeon/radeon_gem.c 2
> -rw-r--r-- drivers/gpu/drm/radeon/radeon_legacy_tv.c 10
> -rw-r--r-- drivers/gpu/drm/radeon/radeon_object.c 2
> -rw-r--r-- drivers/gpu/drm/radeon/radeon_ttm.c 65
> -rw-r--r-- drivers/gpu/drm/radeon/radeon_vm.c</span >
Someone with access to the hw and the platform would have to go through the
changes and see what broke it. A bisect would be an easy way to do it. Also,
it's not necessarily a drm change. It could have been a bad interaction with
some other change elsewhere in the kernel.</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>