https://bugzilla.kernel.org/show_bug.cgi?id=65761 --- Comment #31 from Christoph Haag <haagch.christoph@xxxxxxxxxxxxxx> --- Created attachment 124781 --> https://bugzilla.kernel.org/attachment.cgi?id=124781&action=edit callgrind output from X Not much news: I tried to run X with valgrind --tool=callgrind to try to find out about what it does that results in the radeon gpu clocking higher and going to higher voltage when clicking around with windows like minimizing/restoring with kwin & plasma. Unfortunately it does not happen when X runs in valgrind, the radeon gpu always keeps at the lowest frequency and voltage level. But the runpm status is still "active" all the time with or without valgrind. With the exact same xorg and xf86* builds the clocking higher and raising the voltages happens when it runs not in valgrind... I still post the callgrind log, even if it did not clock higher, because in the Callgraph Blockhandler() calls intel sna stuff but it also calls a lot of radeon stuff. Whether this is something that is caused by valgrind or something that should happen with a radeon gpu that is not configured to be used for anything, I don't know. -- 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
