Re: [gentoo-user] Blank screen after hibernation with radeon driver

[Matti Nykyri]

> On Jun 21, 2015, at 2:16, Fernando Rodriguez <frodriguez.developer@×××××××.com> wrote:
>
> On Saturday, June 20, 2015 10:15:37 AM Matti Nykyri wrote:
>>> On Jun 20, 2015, at 5:16, Fernando Rodriguez
> <frodriguez.developer@×××××××.com> wrote:
>>>
>>> Hello,
>>>
>>> After switching from fglrx to the radeon driver I get a blank screen after
>>> resuming from hibernation. I can ssh in but I can't restart xorg. This
> happens
>>> with pm-utils and also with systemd. Suspend works fine with both.
>>>
>>> My video card is:
>>> VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kabini
>>> [Radeon HD 8210]
>>>
>>> Any suggestions?
>>
>> Ssh in and run commands:
>>
>> export DISPLAY=:0
>> xrandr
>> Or
>> xrandr --output --mode etc with right arguments
>>
>> If that doesn't help, use top and perf top to see what is going on. Does
> restarting X fix te issue?
>
> I can't restart X, it hangs when I try, xrandr also hangs. Even kill -9
> doesn't kill it. The logs sometimes don't show anything at all but today it's
> show this consistently:
>
> un 20 18:19:08 navi kernel: [drm:cik_ring_test] *ERROR* radeon: ring 1 test
> failed (scratch(0x3010C)=0xCAFEDEAD)
> Jun 20 18:19:08 navi kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl
> 300)
> Jun 20 18:19:08 navi kernel: ata1.00: configured for UDMA/133
> Jun 20 18:19:08 navi kernel: [drm:cik_ring_test] *ERROR* radeon: ring 2 test
> failed (scratch(0x3010C)=0xCAFEDEAD)
> Jun 20 18:19:08 navi kernel: [drm] ring test on 3 succeeded in 4 usecs
> Jun 20 18:19:08 navi kernel: [drm] ring test on 4 succeeded in 4 usecs
> Jun 20 18:19:08 navi kernel: [drm] ring test on 5 succeeded in 1 usecs
> Jun 20 18:19:08 navi kernel: [drm] UVD initialized successfully.
> Jun 20 18:19:08 navi kernel: [drm] ring test on 6 succeeded in 812 usecs
> Jun 20 18:19:08 navi kernel: [drm] ring test on 7 succeeded in 3 usecs
> Jun 20 18:19:08 navi kernel: [drm] VCE initialized successfully.
> Jun 20 18:19:08 navi kernel: [drm] ib test on ring 0 succeeded in 0 usecs
> Jun 20 18:19:08 navi kernel: [drm] ib test on ring 3 succeeded in 0 usecs
> Jun 20 18:19:08 navi kernel: [drm] ib test on ring 4 succeeded in 0 usecs
> Jun 20 18:19:08 navi kernel: [drm] ib test on ring 5 succeeded
> Jun 20 18:19:08 navi kernel: [drm] ib test on ring 6 succeeded
> Jun 20 18:19:08 navi kernel: [drm] ib test on ring 7 succeeded
> Jun 20 18:19:08 navi kernel: [drm:radeon_dp_link_train_cr] *ERROR* displayport
> link status failed
> Jun 20 18:19:08 navi kernel: [drm:radeon_dp_link_train_cr] *ERROR* clock
> recovery failed
> Jun 20 18:19:08 navi kernel: [drm:radeon_dp_link_train_cr] *ERROR* displayport
> link status failed
> Jun 20 18:19:08 navi kernel: [drm:radeon_dp_link_train_cr] *ERROR* clock
> recovery failed
>
> --------
>
> On one occassion there where about 20 backtraces on the log. That log is gone
> but it had a message basically saying (I don't remember the exact words) that
> something went wrong and the kernel recovered but a reboot was still needed.
> I'll post if it comes up again.
>
> Also relevant that I've been getting this and similar errors on my logs for a
> few days (probably since I switched to the radeon driver), all the i2c devices
> are on the video card:
>
> Jun 20 16:46:30 navi kernel: i2c i2c-7: sendbytes: error -110
> Jun 20 16:46:41 navi kernel: i2c i2c-7: sendbytes: error -110
> Jun 20 16:47:01 navi kernel: i2c i2c-7: sendbytes: error -110
> Jun 20 16:47:11 navi kernel: i2c i2c-7: sendbytes: error -110
> Jun 20 16:47:31 navi kernel: i2c i2c-7: sendbytes: error -110

What is the output of:

perf top

Do you have kernel debugging symbols compiled in? If then do kernel function trace.

See what an strace to X shows.

-- 
-Matti