I can confirm that this is a problem. It was reported to me yesterday (https://github.com/jlund/streisand/issues/89) and is affecting upgraded instances at several providers. I have tested new servers at AWS, DigitalOcean, and Linode with the same results.
Temporarily downgrading to `linux-image-3.2.0-4-amd64=3.2.63-2` solves the issue for me as well. Josh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
