https://bugs.freedesktop.org/show_bug.cgi?id=78717
Priority: medium Bug ID: 78717 Assignee: dri-devel@lists.freedesktop.org Summary: radeon: Failed to allocate a buffer Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mmstickman@gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.1 Component: Drivers/Gallium/radeonsi Product: Mesa
When you set shadows to Ultra in the recently released open source game, Tesseract, the game will segfault with the following:
radeon: Failed to allocate a buffer: radeon: size : 536870912 bytes radeon: alignment : 32768 bytes radeon: domains : 4 radeon: Failed to allocate a buffer: radeon: size : 536870912 bytes radeon: alignment : 32768 bytes radeon: domains : 4 radeon: Failed to allocate a buffer: radeon: size : 536870912 bytes radeon: alignment : 32768 bytes radeon: domains : 4 radeon: Failed to allocate a buffer: radeon: size : 536870912 bytes radeon: alignment : 32768 bytes radeon: domains : 4 radeon: Failed to allocate a buffer: radeon: size : 536870912 bytes radeon: alignment : 32768 bytes radeon: domains : 4 radeon: Failed to allocate a buffer: radeon: size : 536870912 bytes radeon: alignment : 32768 bytes radeon: domains : 4 failed allocating shadow atlas!
MSAA also seems to hang the entire machine
https://bugs.freedesktop.org/show_bug.cgi?id=78717
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Product|Mesa |DRI Version|10.1 |unspecified Component|Drivers/Gallium/radeonsi |DRM/Radeon
--- Comment #1 from Michel Dänzer michel@daenzer.net --- This is probably due to the kernel radeon driver refusing to allocate BOs larger than the CPU mappable part of VRAM. Please attach the output of dmesg after the problem occurs.
MSAA also seems to hang the entire machine
That would need to be tracked in a separate report.
https://bugs.freedesktop.org/show_bug.cgi?id=78717
--- Comment #2 from mmstickman@gmail.com --- The output of dmesg when the crash occurs is:
[106117.559369] radeon_gem_object_create:62 alloc size 512Mb bigger than 256Mb limit [106117.559470] radeon_gem_object_create:62 alloc size 512Mb bigger than 256Mb limit [106117.559714] radeon_gem_object_create:62 alloc size 512Mb bigger than 256Mb limit
https://bugs.freedesktop.org/show_bug.cgi?id=78717
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|radeon: Failed to allocate |radeon: Failed to allocate |a buffer |a buffer with Tesseract
https://bugs.freedesktop.org/show_bug.cgi?id=78717
--- Comment #3 from Michel Dänzer michel@daenzer.net --- 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 need to specify radeon.gartsize=1024 or larger on the kernel command line.
https://bugs.freedesktop.org/show_bug.cgi?id=78717
jackdachef@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jackdachef@gmail.com
--- Comment #4 from jackdachef@gmail.com --- potential fix for glamor that might fix this from a non-kernel approach (at least it did for me):
https://bugs.freedesktop.org/show_bug.cgi?id=71190
https://bugs.freedesktop.org/show_bug.cgi?id=78717
--- Comment #5 from Boyd Stephen Smith Jr. Boyd.Stephen.Smith.Jr@GMail.com --- 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 256Mb limit [154272.661012] radeon_gem_object_create:62 alloc size 340Mb bigger than 256Mb limit [154272.661020] radeon_gem_object_create:62 alloc size 340Mb bigger than 256Mb limit
They match the similar errors I'm getting from (modded) Minecraft:
[16:08:10] [Client thread/ERROR]: ########## GL ERROR ########## [16:08:10] [Client thread/ERROR]: @ Post render [16:08:10] [Client thread/ERROR]: 1285: Out of memory [16:08:10] [Client thread/ERROR]: ########## GL ERROR ########## [16:08:10] [Client thread/ERROR]: @ Post render [16:08:10] [Client thread/ERROR]: 1285: Out of memory [16:08:10] [Client thread/ERROR]: ########## GL ERROR ########## [16:08:10] [Client thread/ERROR]: @ Post render [16:08:10] [Client thread/ERROR]: 1285: Out of memory [16:08:10] [Client thread/ERROR]: ########## GL ERROR ########## [16:08:10] [Client thread/ERROR]: @ Post render [16:08:10] [Client thread/ERROR]: 1285: Out of memory
I'm on Debian Jessie, but I should be able to figure out how to run a newer X or kernel for testing, if needed.
https://bugs.freedesktop.org/show_bug.cgi?id=78717
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #6 from Michel Dänzer michel@daenzer.net --- This seems to work fine with current versions of kernel and Mesa.
https://bugs.freedesktop.org/show_bug.cgi?id=78717
--- Comment #7 from Boyd Stephen Smith Jr. Boyd.Stephen.Smith.Jr@GMail.com --- 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.
https://bugs.freedesktop.org/show_bug.cgi?id=78717
--- Comment #8 from Michel Dänzer michel@daenzer.net --- (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.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org