So, to sum up my current testing (_ok_=noproblem, KO=delay+missed events):
- Lucid 10.04.4 : _ok_ - Natty 11.04 : KO - Oneiric 11.10 : KO - Precise: - KO in 3.2.0.23 ubuntu-sauced kernel - KO in mainline 3.2.15 kernel found at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.15-precise/ - _ok_ with mainline 3.4.0-rc3 kernel found at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/ - Then "If I remember correctly this bug was solved by an update somewhere in april~july 2012" - Raring 13.04 : KO - Saucy: - KO with saucy-desktop-i386.iso from 2013-05-13 (uname -r reports "3.9.0-1-generic") - KO with mainline v3.10-rc1-saucy from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc1-saucy/ (uname -r reports "3.10.0-031000rc1-generic")
So, to sum up my current testing (_ok_=noproblem, KO=delay+missed events):
- Lucid 10.04.4 : _ok_ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.2.15- precise/ kernel. ubuntu. com/~kernel- ppa/mainline/ v3.4-rc3- precise/ i386.iso from 2013-05-13 (uname -r reports "3.9.0-1-generic") kernel. ubuntu. com/~kernel- ppa/mainline/ v3.10-rc1- saucy/ (uname -r reports "3.10.0- 031000rc1- generic" )
- Natty 11.04 : KO
- Oneiric 11.10 : KO
- Precise:
- KO in 3.2.0.23 ubuntu-sauced kernel
- KO in mainline 3.2.15 kernel found at http://
- _ok_ with mainline 3.4.0-rc3 kernel found at http://
- Then "If I remember correctly this bug was solved by an update somewhere in april~july 2012"
- Raring 13.04 : KO
- Saucy:
- KO with saucy-desktop-
- KO with mainline v3.10-rc1-saucy from http://