I've heard of this problem with early 2.4.x kernels. Nobody's reported it with 2.2.x, and it's fixed in current 2.4.x kernels. I've had no problems in six months under 2.2.18.