It turns out, "Linux 2.6.36.1-mine #1 SMP Sat Dec 4 12:56:31 CST 2010 x86_64 GNU/Linux" does not have this issue.
uptime: 15:40:40 up 5 days, 18:11, 9 users, load average: 0.63, 0.49, 0.40
There is the same entry in the kern.log seen in ver. 35 (not seen in 37-rc3).
Dec 4 22:03:04 my kernel: [ 2051.693528] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Dec 4 22:15:09 my kernel: [ 2777.127673] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
It turns out, "Linux 2.6.36.1-mine #1 SMP Sat Dec 4 12:56:31 CST 2010 x86_64 GNU/Linux" does not have this issue. mode_getfb] *ERROR* invalid framebuffer id mode_getfb] *ERROR* invalid framebuffer id
uptime: 15:40:40 up 5 days, 18:11, 9 users, load average: 0.63, 0.49, 0.40
There is the same entry in the kern.log seen in ver. 35 (not seen in 37-rc3).
Dec 4 22:03:04 my kernel: [ 2051.693528] [drm:drm_
Dec 4 22:15:09 my kernel: [ 2777.127673] [drm:drm_
It could be associated with this bug https:/ /bugs.launchpad .net/bugs/ 593463. So fixing this bug (if it is?) introduces the current one?