Okay, this is interesting. I found that I can confirm this bug on Saucy using the 3.8.13.12 mainline kernel version, which according to http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html is equivalent to the 3.8.0-34.49 kernel I used in my test of updated Raring (and there was no bug there). I expected the 3.8.13.13 kernel to exhibit the bug (it does as well) and the 3.8.13.12 kernel to not show it based on what I saw in Raring, so this surprised me.
Is it possible that this bug is not due to the kernel?
Okay, this is interesting. I found that I can confirm this bug on Saucy using the 3.8.13.12 mainline kernel version, which according to http:// kernel. ubuntu. com/~kernel- ppa/info/ kernel- version- map.html is equivalent to the 3.8.0-34.49 kernel I used in my test of updated Raring (and there was no bug there). I expected the 3.8.13.13 kernel to exhibit the bug (it does as well) and the 3.8.13.12 kernel to not show it based on what I saw in Raring, so this surprised me.
Is it possible that this bug is not due to the kernel?