https://bugs.freedesktop.org/show_bug.cgi?id=67187
--- Comment #5 from Harald Judt h.judt@gmx.at --- Created attachment 83279 --> https://bugs.freedesktop.org/attachment.cgi?id=83279&action=edit dmesg.out
Ok, I gave it a try with new vanilla 3.11-rc3. It ends with the following error message, though I'm not sure it isn't simply a follow-up problem caused by previous errors:
[ 2203.028013] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
As you can deduce from the dmesg.out file attached to the bug report, the first few tries work ok. The problem seems to be more easily reproducible (but not restricted to that) when pm_async is enabled. I'm not yet sure it happens with pm_async off, but by experience, the chances that it does are very likely.
What is a bit strange is that the message "entering sleep state S4" never appears in the dmesg.out. This _could_ be because I issued "echo reboot > /sys/power/disk". However, this is about hibernate/resume, as you can see when you look at the pm messages.
I believe the main problem occurs already at suspend time, because when it happens, suspend always takes longer than usual, hanging a bit with the monitor turned off. However, there are no error messages to be found in the log, only when resuming. Perhaps I should use no_suspend_console and/or net_console.
Also note how the UVD initialization fails, then the machine continues booting and later you can hibernate again, which will restore UVD but cause the ring 0 failure with CAFEDEAD. At first, the screen is blank, then shows an animated nostalgic noise picture similar to analog tv that has no reception. The machine is still responsive and one can ssh in.
Is there perhaps an option to enable for more debugging messages that could give more insight?