> Then I doubt that it is a kernel problem at all. The ssh connection > would not survive corruption in deeper layers. > > Please use memtest86 to test if you don't have broken memory.
I'm not going to say it's not possible - I've been using Linux a long time, and know about compiling floppy.c as a torture test. On the other hand, this machine has been stable for 3 years, with a variety of kernels, 64 bit, 32 bit, also in windows, is used with high cpu load frequently, etc. It has been rock solid. I installed a new kernel, immediately experienced problems, boot back to the old kernel, and problems go away. Occam points at the new kernel. (And yes, I get the new kernel could point to an underlying issue, could be heating the CPU differently, or something - but it doesn't feel like the most likely scenario to me.) It could also be that it's not in the network stack but some other kernel issue. Thanks, Dale -- Dale E. Martin - [EMAIL PROTECTED] http://the-martins.org/~dmartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
