On Wed, 2012-04-18 at 10:20 -0700, Jesse Barnes wrote: > This indicates an internal messaging issue between the CPU and PCH, but > there's nothing the driver can do about it. We seem to be able to > trigger it at hotplug time sometimes, possibly due to the interrupt > corrupting an in-flight message between CPU and PCH. At any rate, the > error is harmless, so there's no need to bother the user about it.
I'm unconvinced. The bugs I've seen tend to have these messages in combination with actual output setup problems. If that's going to be reliably true I'd just as soon always see the message without needing drm.debug=7. - ajax
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
