This seems to be fixed in unstable with intel 2:2.9.0-1. I'm also now running 2.6.31, so maybe it was a kernel-side fix. I'm not marking the bug as done because it's still open upstream, so it might just be a co-incidence that it appears to be fixed. :) -- Sam Morris <sam@robots.org.uk>