Resume on this machine works fine when I boot with init=/bin/bash or if I boot to init 3 and blacklist radeon module. However when booting into init 3 with radeon module loaded resume works partially. When resuming from RAM I can see console for half a second and then it disappears. In that half a second backlight seems to be lower as well, which is fine for me, but maybe will give you some idea?
Created attachment 32783 [details] dmesg
Created attachment 32784 [details] regs dump before suspend
Created attachment 32785 [details] regs dump after resume got it by ssh
Created attachment 32786 [details] diff -u init3.after.log init3.before.log
Is this possible that just after resume radeon loads everything fine, but then some other module overwrites it's work? On the other hand keep in mind that blacklisting radeon makes resume work fine... Weird. Can I provide more info for debugging it?
Oh, what I use is: commit c8c15ff1e90bfc4a2db1ba77a01b3b2783e723fc Author: Jerome Glisse <jglisse@redhat.com> Date: Mon Jan 18 13:01:36 2010 +0100 drm/radeon: r6xx/r7xx possible security issue, system ram access
Hm, the same bug happens on different notebook with RV620... Maybe it's something in openSUSE that causes this? Both run this distribution.
The problem is that pm-suspend (s2ram?) uses quriks even for KMS. It tries to restore GPU state in KMS, where it's already handled by KMS GPU driver. Forcing pm-suspend to do not use quirks fixes problem. See bug #26235 for details
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.