It sounds like this bug does not exist with kernel 3.7.10 per comment #7.
Do you happen to know if this bug was introduced in v3.8, and if so, what release candidate? If you don't know, can you test some v3.8 kernels to identify when this bug was introduced:
It sounds like this bug does not exist with kernel 3.7.10 per comment #7.
Do you happen to know if this bug was introduced in v3.8, and if so, what release candidate? If you don't know, can you test some v3.8 kernels to identify when this bug was introduced:
v3.8-rc1: http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.8-rc1- raring/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.8-rc4- raring/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.8-raring/
v3.8-rc4: http://
v3.8 final: http://