Comment # 12 on bug 82527 from Jamie Heilman

I can confirm that the regression reported in comment #2 that I bisected to
d55b4af909bc16f7982c2b8b8656f0898158627b is now fixed as of
80ad99da8bd213e12b925407f1c97a303aa8f87f (which pulled in
5838ae610ff36777b8fce6f353c2417980c1a1fa).  Additionally I haven't been able to
reproduce the case that this bug was originally opened for yet, (prior to 3.17
I could but it was always a bit finicky).  Still, it's probably too early to
say that its fixed for sure; I have a slightly different card than Martin's (a
10de:042f, NVIDIA Corporation G86 [Quadro NVS 290] (rev a1)).