Just a little update on this bug.

Still experiencing this problem with the latest upstream kernel code (up to
33b40178cb3bd75294d1a758b3f509a0d38682ab)

It was mentioned on irc that the output of xrandr --verbose may be useful. So
I've also attached two additional files with DVI-I-0 in either a
working/nonworking state.