As mentioned in comment #19 this bug disappeared with kernel 3.13.0-32, but now it resurfaced with 3.13.0-44. It had no problems with the previous version 3.13.0-43 though.
As mentioned in comment #19 this bug disappeared with kernel 3.13.0-32, but now it resurfaced with 3.13.0-44. It had no problems with the previous version 3.13.0-43 though.