Comment 24 for bug 908856

I've since updated from F16 to F18 (and all the kernel/driver updates that entails) on the same hardware, and it appears the problem no longer occurs for me. I verified it works with or without the workaround in place.