@Hernando
Can you reproduce the bug, then post your /var/log/syslog? That will give me more to search with upstream.
Searching on with only "[drm:drm_mode_getfb] *ERROR* invalid framebuffer id" Only suggests one commit, but it is related to ftrace:
ftrace: Fix regression of :mod:module function enabling commit 43dd61c9a09bd413e837df829e6bfb42159be52a upstream.
@Raul Do you see any other errors when this happens besides "[drm:drm_mode_getfb] *ERROR* invalid framebuffer id"?
We know that this bug exists in the 3.0 until 3.2 kernels, and it is fixed in upstream 3.3.
@Hernando Do you think you can test the other v3.3 release candidates? Maybe v3.3-rc1 to see if we can narrow down when the fix was introduced?
@Hernando
Can you reproduce the bug, then post your /var/log/syslog? That will give me more to search with upstream.
Searching on with only "[drm:drm_ mode_getfb] *ERROR* invalid framebuffer id" Only suggests one commit, but it is related to ftrace:
ftrace: Fix regression of :mod:module function enabling 3e837df829e6bfb 42159be52a upstream.
commit 43dd61c9a09bd41
@Raul mode_getfb] *ERROR* invalid framebuffer id"?
Do you see any other errors when this happens besides "[drm:drm_
We know that this bug exists in the 3.0 until 3.2 kernels, and it is fixed in upstream 3.3.
@Hernando
Do you think you can test the other v3.3 release candidates? Maybe v3.3-rc1 to see if we can narrow down when the fix was introduced?