Subject says it all really. Latest git commit is: commit fb53f8621a3fab88776ae2450a1f3afc7920231b Author: Jerome Glisse <jglisse@redhat.com> Date: Wed Dec 9 21:55:10 2009 +0100 drm/ttm: Print debug information on memory manager when eviction fails This add helper function to print information on eviction placements and memory manager status when eviction fails to allocate memory space. Signed-off-by: Jerome Glisse <jglisse@redhat.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
Created attachment 31927 [details] dmesg output
Created attachment 31933 [details] [review] verbose debug Please run with the attached patch and attach new full dmesg
Created attachment 31934 [details] dmesg output with patch Output of dmesg with the debugging patch and one of the error messages
Created attachment 31939 [details] Xorg configuration file
Created attachment 31940 [details] [review] Allow to allocate bo from system ram Please try with this patch, hopefully validation have more chance of succeeding than allocation.
Created attachment 31975 [details] kernel output after a day's uptime After a day, the major problems have lessened. However, there are still the same kind of screen corruptions going on but at a lower frequency. I'm still getting the following error messages from the kernel: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation ! [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation ! [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation !
(In reply to comment #5) > Created an attachment (id=31940) [details] > Allow to allocate bo from system ram > > Please try with this patch, hopefully validation have more chance of succeeding > than allocation. > Patch fixes the issue for me so far: RS880 + 2.6.32 + drm-radeon-testing.
Just to add, I also still get: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation ! [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation ! [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation ! [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation ! But no evident corruption.
Created attachment 32032 [details] corruption in Konversation I spoke too soon. After 5-10 mins the system gradually went foobar. Here's an example in konversation, but the corruption was all over kde, chromium, thunderbird. And it's persistent corruption, changing window did not help. Same errors in dmesg as above: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation !
this happens to me too after some hours of usage, rv770, amd64, drm-radeon-testing, everything from git master.
(In reply to comment #9) > Created an attachment (id=32032) [details] > corruption in Konversation Yeah, this is exactly the corruption I get at the same time as the errors.
With a rs780 (790gx based hd3300) I get corruption similar to the attachment right from X startup. Bisecting (manually) found 779720a3209849be202ac36a811e934865c50971 was causing the problem. Reverting this fixed things here. Hope this helps.
Most likely same as bug #25567
After being up several hours with commit causing corruption at startup reverted I am beginning to see some corruption very much like the attachments...
please try the patch on bug 25567
(In reply to comment #15) > please try the patch on bug 25567 > is this to apply on top of glisse's patch? http://bugs.freedesktop.org/attachment.cgi?id=31940
(In reply to comment #5) > Created an attachment (id=31940) [details] > Allow to allocate bo from system ram > > Please try with this patch, hopefully validation have more chance of succeeding > than allocation. > This patch is not in drm-radeon-testing yet. Why? And it does not apply to it either. Hence dmesg is still full of: radeon 0000:01:05.0: object_init failed for (7983104, 0x00000004) [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (7983104, 4, 4096) On the other side, the *ERROR* Failed to parse relocation is fixed.
nevermind, i did not have all the patches from drm-radeon-testing. It works fine now, no extra patches needed :)
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.