It was most likely a kernel problem. I've not had any recent reports of this, so will close it unless it appears again.
It was most likely a kernel problem. I've not had any recent reports of this, so will close it unless it appears again.