Hi, It looks like an i915 commit causes problems with frequency scaling to happen to people.
Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.
--- Begin Message ---https://bugzilla.kernel.org/show_bug.cgi?id=58971 --- Comment #42 from Alexander Kaltsas <[email protected]> 2013-06-10 14:53:06 --- Ok, I managed to complete a git bisect. The result was: First bad commit: [15239099d7a7a9ecdc1ccb5b187ae4cda5488ff9] drm/i915: enable irqs earlier when resuming. http://o.cs.uvic.ca:20810/perl/cid.pl?cid=15239099d7a7a9ecdc1ccb5b187ae4cda5488ff9 I removed the above patch from kernel 3.9.4, 3.9.5 and it seems to work ok after suspend and resume. With Intel PSTATE enabled. The temperature is back to normal and the cpu frequency doesn't "lock" to the highest value. Just a side note. Don't know if related at all: I have noticed that when using Intel PSTATE. If the system starts with frequency scaling to powersave the frequency is around to 800~900 MHz. If I change it to performance it will go up. After changing it back to powersave the frequency will stay to ~2000 MHz. If I suspend and resume it will be around to 800~900 MHz again. This doesn't seem to effect the temperature of the system' -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
--- End Message ---
_______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
