This might be related to me using 2.6.20-9, rather than 2.6.20-10. I've been using -9 due to a kernel bug (turned out to be a severe issue in the kvm module, which I was autoloading at boot), and having booted into -10, this problem seems to have disappeared.
This might be related to me using 2.6.20-9, rather than 2.6.20-10. I've been using -9 due to a kernel bug (turned out to be a severe issue in the kvm module, which I was autoloading at boot), and having booted into -10, this problem seems to have disappeared.