Comment 8 for bug 127168

No worries Leann, I'll do it tonight (in about 10 hours).

I think this issue is actually pretty much the same as 129910 (tagged Critical) anyway, since that is certainly the effect I see here. But then, I didn't raise either this bug or 129910, and I don't know if Bugdan or Joshua would agree with my assessment. I'm not disputing the Won't Fix, just something else I observed that seems to ring a bell here.

Where would be the best place to update with my test results? On this bug (127168), or the kernel task (number?), or elsewhere?

Also, a pair of work-arounds for anyone searching the bug database who comes accross this. There are two that have worked for me (ether one is sufficient, don't need both):

1) remove your vga=xxx option and put up with low-res 80x25 VTTY screens for now
2) hardware solution (if you can): use DVI cable to your LCD, to avoid refresh speed issue over VGA.

Neither is a solution, just a work-around. YMMV.