Created attachment 87293 [details] syslog during crash Firefox 24, with hardware acceleration on, X crashes and the whole desktop enters a logout loop. Restarting is the only way out :(. I am running Ubunut 13.04 (linux mint 15) with Linux Kernel 3.11.4 with radeon.dpm=1 and oibaf ppa (mesa-9.3-git) and Xorg 1.13.4 Attached are my syslog and Xorg.0.log during the crash. Please let me know if I need to attach any further logs. Here are some error messages that I found in these logs : syslog : [ 1807.720765] [drm:radeon_crtc_page_flip] *ERROR* failed to pin new rbo buffer before flip [ 1810.600061] radeon 0000:01:00.0: ffff88008c51ac00 pin failed from Xorg.0.log : [ 1839.182] (WW) RADEON(0): flip queue failed: Invalid argument [ 1839.182] (WW) RADEON(0): Page flip failed: Invalid argument
Created attachment 87294 [details] Xorg.0.log attached xorg.0.log after crash
Yeah I've just experienced the same... it's a shock that firefox seems to be responsible for the bug. This is a really critical bug. I've got quite the same warnings: radeon 0000:0b:00.0: ib ring test failed (-35). [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). radeon 0000:0b:00.0: GPU lockup (waiting for 0x0000000000447fb3 last fence id 0x0000000000447fac) radeon 0000:0b:00.0: GPU lockup CP stall for more than 10000msec [...] [drm:radeon_crtc_page_flip] *ERROR* failed to pin new rbo buffer before flip radeon 0000:0b:00.0: ffff880158860c00 pin failed Lots of errors like that!
Is this still happening with current versions of Mesa and the kernel?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/395.
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.