On Tue, 31 Jul 2012 09:06:42 +0100, James Bottomley James.Bottomley@HansenPartnership.com wrote:
Actually, bad news: it looks like the problem is drm:
on 3.5 killing X causes idle power to go 14W -> 5.9W on 3.4.6 killing X causes idle power to go 6.8W -> 5.7W
The files that will be the most interesting to compare at first are:
/sys/kernel/debug/dri/0/i915_drpc_info /sys/kernel/debug/dri/0/i915_cur_delayinfo /sys/kernel/debug/dri/0/i915_fbc_status
However if it was simple regression in drm, then the bisect would have continued to work despite the merge point jumping between 3.4 and 3.5, right?
Thanks, -Chris