Comment 177 for bug 359392

@Bryce
Your last hang is right after a render accel request again (the GPU dump indicates that), but the interrupt state and such look ok:
Interrupt enable: 00020053 <- user interrupts are on, which is good since we use those to wait for requests to complete
Interrupt identity: 00000000 <- no interrupts pending atm, which should be ok
Interrupt mask: fffcdfac
Pipe A stat: 00040000 <- pipe stats shouldn't matter here, but fwiw vblank interrupts are on
Pipe B stat: 00000206 <- and one has occurred on pipe B
Interrupts received: 308241 <- interrupt count seems reasonable (you'll get lots of them)
Current sequence: 553893 <- hw finished with request # 553893
Waiter sequence: 553897 <- most recent request #
IRQ sequence: 553890 <- most recently signalled request completion (should be <= current sequence, so it's ok)

The active request list looks ok too, the seqnos are all in the future though, which means software is still waiting for rendering to complete... Just to confirm, if you repeatedly cat i915_gem_interrupt you don't see the interrupts received or any of the sequence numbers change?