<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Rv6xx dpm problems" href="https://bugs.freedesktop.org/show_bug.cgi?id=66963#c252">Comment # 252</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Rv6xx dpm problems" href="https://bugs.freedesktop.org/show_bug.cgi?id=66963">bug 66963</a> from <a class="email" href="mailto:kap3tan@gmail.com" title="Kajzer <kap3tan@gmail.com>"> Kajzer</a> <pre>(In reply to Alex Deucher from <a href="show_bug.cgi?id=66963#c251">comment #251</a>) > (In reply to Kajzer from <a href="show_bug.cgi?id=66963#c250">comment #250</a>) > > With kernels 3.17 and 3.18 I have freezes when playing some games, those > > freezes can happen somewhere between 10 minutes and 1 hour. > > Freeze occur only in games. > > With kernel 3.16 everything is normal and there are no freezes. > > Latest patch (auto->high and radeon.dpm=1) is used in each of those kernels. > > Everything else is exactly the same, just booting with different kernel > > makes a difference. > > Can you bisect? I can try, never done that. I'm on gentoo and I guess I'll follow this guide for bisecting : <a href="http://wiki.gentoo.org/wiki/Kernel_git-bisect">http://wiki.gentoo.org/wiki/Kernel_git-bisect</a> I'm using these kernel versions : [1] linux-3.16.7-gentoo * [2] linux-3.17.7-gentoo [3] linux-3.18.1-gentoo I'll mark 3.16.7 as good and 3.17.7 as bad, might take some time though because there are lots of patches between those two versions. My guess is that 3.18 picked up whatever was bad for this bug from 3.17 I'll try to do this ASAP but it might take some time. This line from that bisect guide got me scared : "Try to narrow the versions down as much as possible before starting the bisect, you might need to recompile the kernel a lot of times otherwise." If you know any faster way or have any suggestion please do tell. It might be easier (for me) if I can see somewhere changes in radeon only (3.16 -> 3.17) and then compile the kernel with or without those changes until I find which one is a culprit.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>