I've just found out that the problem persists on kernel 2.6.32-bpo.5-686, but not on 2.6.32-bpo.5-amd64.