Comment # 11
on bug 83616
from Dieter Nützel
(In reply to comment #10) > (In reply to comment #7) > > This fixes ONE of the bugs Christian and me are hunting for some days, now. > > Making my RV730 AGP (!!!) working with 3.17-rcX/drm-next-3.18-wip, again. > > > > Crashed with mplayer -vo vdpau XXX immediatly. > > > > But 'allow UVD to use a second 256MB segment' gave no speedup, at least for > > me. > > > > Maybe it is the 'second' bug (regression) introduced with the switch from > > 3.16 to 3.17 (drm-next). > > > [snip] > > > > Tried after bisection with reverting: > > drm-radeon-fix-display-handling-in-radeon_gpu_reset.patch > > > > Any ideas, Alex/Christian? > > I'm not sure what you are asking. What issue are you having? Sorry Alex, but is this intended (it is in the logs since 3.16+, too)? [ 11.316570] radeon 0000:01:00.0: (-1) pin WB bo failed [ 11.316582] radeon 0000:01:00.0: f2fb0c00 unpin not necessary [ 11.316601] radeon 0000:01:00.0: disabling GPU acceleration [ 11.369220] radeon 0000:01:00.0: f6064000 unpin not necessary [ 11.433188] [TTM] Finalizing pool allocator [ 11.433309] [TTM] Zone kernel: Used memory at exit: 0 kiB [ 11.433317] [TTM] Zone highmem: Used memory at exit: 0 kiB [ 11.433320] [drm] radeon: ttm finalized [ 11.433325] [drm] Forcing AGP to PCIE mode So, maybe GTT/GART grows to big?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
