Bug 78287 - [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
Summary: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r300 (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2014-05-05 09:07 UTC by Piero Finizio
Modified: 2014-05-12 14:00 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

dmesg.txt (229.74 KB, text/plain)
2014-05-05 09:07 UTC, Piero Finizio

Description Piero Finizio 2014-05-05 09:07:20 UTC
Created attachment 98460 [details]

Description of problem:
On Second Life, 3D virtual world, I get recursively in dmesg the follow error message "[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!..." with subsequent Call Trace.

Version-Release number of selected component (if applicable):
OS: Fedora 20, Kernel: 3.15.0-0.rc3.git0.1.fc21.i686 (i686), Desktop: KDE 4.12.4, libdrm-2.4.54, Display Server: X Server 1.14.4, Display Driver: radeon 7.3.99, OpenGL: 2.1 Mesa 10.3.0-devel (git-829cb04) Gallium 0.4, Compiler: GCC 4.8.2 20131212 + LLVM 3.4,

How reproducible:
Logging in Second Life

Steps to Reproduce:
1.Choosing a crowded Sim
2.Moving around
3.Rebuilding the 3D objects from cache

Actual results:
I don't have disconnections but frequent, empty frames with stuttering

Expected results: Stable rebuilding

Additional info:
Notebook Asus F3JP with  Graphics: AMD Mobility Radeon X1700 256MB
Comment 1 Marek Olšák 2014-05-05 11:32:01 UTC
The error means there is not enough video memory.
Comment 2 Piero Finizio 2014-05-05 14:27:10 UTC
Thank you very much for your ready response and overall, for your effective application to Mesa-OpenGl world,  Marek Olšák.
Comment 3 Mantas Mikulėnas 2014-05-10 14:56:01 UTC
(In reply to comment #1)
> The error means there is not enough video memory.

Does it always? I know -12 is ENOMEM, but I'm frequently getting the same error even though `radeontop` shows only about 200-250 MB out of 1 GB used.
Comment 4 Alex Deucher 2014-05-12 14:00:04 UTC
In this actually a failure to allocate regular system memory (kalloc or drm_malloc_ab).

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.