There was a period recently where this was happening to me quite frequently. It seems to have been behaving itself lately though. Actually, I think it's been since Mark discovered the suspected problem code in the kernel.