On Fri, 2015-06-26 at 14:43 -0700, Linus Torvalds wrote:
On Thu, Jun 25, 2015 at 6:00 PM, Dave Airlie airlied@linux.ie wrote:
This is the main drm pull request for v4.2.
It seems to work ok for me, but it causes quite a few new warnings on my Sony VAIO Pro laptop. It's (once more) a regular i5-4200U CPU (aka Haswell, aka 4th gen Intel Core i5)
Most of them are in check_crtc_state(), and I currently have 18 of these in my log:
[drm:check_crtc_state [i915]] *ERROR* mismatch in dpll_hw_state.wrpll (expected 0x90280202, found 0x00000000) WARNING: CPU: 0 PID: 115 at drivers/gpu/drm/i915/intel_display.c:12319 check_crtc_state+0x8be/0xf60 [i915]() pipe state doesn't match!
but there's a few others too:
WARNING: CPU: 3 PID: 1871 at drivers/gpu/drm/i915/intel_display.c:1362 hsw_disable_ips+0x34/0x160 [i915]() plane A assertion failure (expected on, current off)
WARNING: CPU: 3 PID: 1871 at drivers/gpu/drm/drm_irq.c:1162 drm_wait_one_vblank+0x148/0x1a0 [drm]() vblank not available on crtc 0, ret=-22
and the backtraces aren't all that interesting, but I'm attaching the cleaned-up dmesg, duplicate callchains and all.
Please provide a full dmesg with drm.debug=0x1f in the kernel command line.
Thanks, Ander