https://bugs.freedesktop.org/show_bug.cgi?id=78717
--- Comment #8 from Michel D�nzer ---
(In reply to Boyd Stephen Smith Jr. from comment #7)
> Any hint about when kernel (or mesa) version fixed this?
The BO allocation size limit was lifted in kernel 3.17. Mesa shouldn't matter
after all.
--
https://bugs.freedesktop.org/show_bug.cgi?id=78717
--- Comment #7 from Boyd Stephen Smith Jr.
---
Any hint about when kernel (or mesa) version fixed this? I'd like to upgrade,
but it could ease my way if I didn't have to go all the way to git HEAD.
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=78717
Michel D�nzer changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=78717
--- Comment #5 from Boyd Stephen Smith Jr.
---
Getting a lot of these in my dmesg:
[154272.660917] radeon_gem_object_create:62 alloc size 340Mb bigger than 256Mb
limit
[154272.660925] radeon_gem_object_create:62 alloc size 340Mb bigger than 256
https://bugs.freedesktop.org/show_bug.cgi?id=78717
jackdachef at gmail.com changed:
What|Removed |Added
CC||jackdachef at gmail.com
--- Com
https://bugs.freedesktop.org/show_bug.cgi?id=78717
--- Comment #3 from Michel D?nzer ---
Created attachment 100907
--> https://bugs.freedesktop.org/attachment.cgi?id=100907&action=edit
Hack to allow allocating larger BOs
If you have at least 1G of VRAM, this hack might help. You might also nee
https://bugs.freedesktop.org/show_bug.cgi?id=78717
Alex Deucher changed:
What|Removed |Added
Summary|radeon: Failed to allocate |radeon: Failed to allocate
