Created attachment 856856 [details] dmesg I have an AMD A4-3400 APU with Radeon HD 6410D (Evergreen). I can't login into my desktop because the display looks corrupted after plymouth ends and, I guess, GDM starts. I don't know if the problem is in the ati driver or in the radeon drm. This information error appears in dmesg: ... [ 27.887893] radeon 0000:00:01.0: GPU lockup CP stall for more than 10000msec [ 27.887907] radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000000003 last fence id 0x0000000000000001) ... [ 37.797192] radeon 0000:00:01.0: GPU lockup CP stall for more than 10000msec [ 37.797206] radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000000004 last fence id 0x0000000000000002) [ 37.797214] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [ 37.797222] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [ 37.797228] radeon 0000:00:01.0: ib ring test failed (-35). ... I have trying to disable AGP writeback with radeon.no_wb but hasn't any effect, the wb mode was enabled anyway. Kerner version 3.12.8-300 from F20. xorg-x11-drv-ati 7.2.0 from F20. Some info: # lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] # lsmod | grep radeon radeon 1329346 3 i2c_algo_bit 13257 1 radeon drm_kms_helper 50287 1 radeon ttm 79787 1 radeon drm 283349 5 ttm,drm_kms_helper,radeon i2c_core 38476 5 drm,i2c_piix4,drm_kms_helper,i2c_algo_bit,radeon I have attached dmesg and the Xorg log. Thanks.
Created attachment 856857 [details] Xorg log
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.