Comment # 17
on bug 109345
from Christian Zigotzky
(In reply to Alex Deucher from comment #4) > 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 I see some changes in the GPU memory management subsystem (TTM). Please note: This is a bug report from an enduser. Endusers aren't able to git bisect. They use the distributions for their daily work. I don't have these graphics cards so I can't bisect it ether.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel