(In reply to comment #2)
> Created an attachment (id=34128) [details]
> i915_error_state
>
> Decoded by intel_error_decode at
> http://launchpadlibrarian.net/41062268/IntelErrorDecode.txt . I find two things
> interesting:
> 1. ACTHD: 0x116179c8 which is outside any of the buffers.
Looks like we are reading the wrong register for Active Head on Ironlake when grabbing error state.
> 2. IPEHR: 0x01800002 since I have seen a lot of MI_WAIT_FOR_EVENT "Display Pipe
> A/B Scan Line Window Wait Enable" in this register at other bug reports on i965
> and GM45 lately.
Similarly, I know there has been a lot of poking in this area in order to set up event triggering. Reassigning to a more knowledgeable person.
(In reply to comment #2) launchpadlibrar ian.net/ 41062268/ IntelErrorDecod e.txt . I find two things
> Created an attachment (id=34128) [details]
> i915_error_state
>
> Decoded by intel_error_decode at
> http://
> interesting:
> 1. ACTHD: 0x116179c8 which is outside any of the buffers.
Looks like we are reading the wrong register for Active Head on Ironlake when grabbing error state.
> 2. IPEHR: 0x01800002 since I have seen a lot of MI_WAIT_FOR_EVENT "Display Pipe
> A/B Scan Line Window Wait Enable" in this register at other bug reports on i965
> and GM45 lately.
Similarly, I know there has been a lot of poking in this area in order to set up event triggering. Reassigning to a more knowledgeable person.