I know that the problem appeared after upgrading to 3.8-rc1-drm-next, and continues to exist in the 3.8-rc5-vanilla. async dma is a likely cause.