I'm experiencing the same with linux-image-2.6.32-3-amd64 : 2.6.32-9. Rebooting back to the good linux-image-2.6.32-1-amd64 makes it work. I think this bug should have higher severity priority.