I could not reproduce the bug with linux-image-3.2.0-0.bpo.2-amd64. Seems OK for me, I switched back to linux-image-2.6.32-5-amd64 to see if it will retrigger the bug.