Were you able to test the 3.13.2 kernel, which was posted in comment #9? It would be good to know if the bug still exists with that kernel.
Were you able to test the 3.13.2 kernel, which was posted in comment #9? It would be good to know if the bug still exists with that kernel.