https://bugzilla.kernel.org/show_bug.cgi?id=65761 --- Comment #7 from Christoph Haag <haagch.christoph@xxxxxxxxxxxxxx> --- Created attachment 117771 --> https://bugzilla.kernel.org/attachment.cgi?id=117771&action=edit Same as "117761: dmesg with drm-fixes-3.12-radeon-poweroff branch", but with rmmod radeon and modprobe radeon Okay, I exited X and from a tty did rmmod radeon. It produced the same error in dmesg than it does on 3.13, see attached file... Then with modprobe radeon I got the GPU lockup CP stall for more than 10000msec, but interestingly only once and then it worked. The radeon gpu was at DynOff then. As soon as I started X, the gpu was powered on to DynPwr again. Not even configured as provideroffloadsink or so, just the X startup and presumably hardware detection powered it up and it does not go back to DynOff. But again, knowing that runpm itself works without errors is encouraging. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
