Comment 14 for bug 496640

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Miguel,
     I think, per your research, that we must conclude that your problem is a separate issue having to do with the driver on your particular hardware. You may need to approach the vendor about issues with it.

jarlostensen,
     Thank you for testing this. I understand that you were not able to duplicate entirely the environment that you initially saw the issue in, but I am glad you are in a good state now.

Jan,
      As you are the original reporter of this issue, and you have indicated that the -18 kernel has resolved the issue for you, I am closing this bug as Fix Committed, since this will be rolled into the next release.

Please feel free to reopen if you feel this is in error.

-JFo