@Warren, thats for testiong the 3.13 upstream stable kernel and confirming it still has the bug. Were you able to confirm the latest mainline kernel, mentined in comment #9 did in fact solve the bug. If it did, then we can perform a "Reverse" bisect to identify the commit that fixes this.
@Warren, thats for testiong the 3.13 upstream stable kernel and confirming it still has the bug. Were you able to confirm the latest mainline kernel, mentined in comment #9 did in fact solve the bug. If it did, then we can perform a "Reverse" bisect to identify the commit that fixes this.