https://bugs.freedesktop.org/show_bug.cgi?id=28402

--- Comment #80 from Da Fox da_fox@mad.scientist.com 2010-10-15 05:05:52 PDT --- (In reply to comment #79)

Created an attachment (id=39455)

View: https://bugs.freedesktop.org/attachment.cgi?id=39455 Review: https://bugs.freedesktop.org/review?bug=28402&attachment=39455

Make sure gtt and vram are not directly adjacent

Does this patch fix the issue?

It should, since it simply puts vram at 0 when it is detected that gtt and vram are adjacent. dmesg says: ---8<--------- radeon 0000:01:00.0: GTT: 256M 0xD0000000 - 0xDFFFFFFF radeon 0000:01:00.0: VRAM: 64M 0x00000000 - 0x03FFFFFF (64M used) --->8--------- so it has moved vram to 0. I'll test it just the same though :) One thing I am wondering is if it is possible to get vram/gtt overlapping with this, since this patch doesn't seem to perform any further checks to ensure this when moving either vram or gtt to 0? Presumable this already handled elsewhere?