[H-GEN] TCPv4 errors increasing in frequency

[Laurence J. Rietberg]

Dear Humbug people,
I thought I'd share this question with you in the hope
that you have some ideas of what might be going on here.

After about 2 days uptime I start to obtain TCPv4 errors in
dmesg such as the following:
TCPv4 bad checksum from 202.139.0.246:caf9 to 130.102.224.1:0050, len=20/20/40
TCPv4 bad checksum from 202.139.0.246:cafa to 130.102.224.1:0050, len=20/20/40
TCPv4 bad checksum from 202.139.0.246:cb45 to 130.102.224.1:0050, len=20/20/40
TCPv4 bad checksum from 172.22.14.37:04b1 to 130.102.224.1:0017, len=21/21/41
TCPv4 bad checksum from 172.22.14.37:04b1 to 130.102.224.1:0017, len=21/21/41
TCPv4 bad checksum from 172.22.14.37:04b1 to 130.102.224.1:0017, len=20/20/40
TCPv4 bad checksum from 172.22.14.37:04b1 to 130.102.224.1:0017, len=21/21/41
TCPv4 bad checksum from 172.22.14.37:04b1 to 130.102.224.1:0017, len=21/21/41
Socket destroy delayed (r=0 w=1632)
...

I have been told by others that this is rather harmless and may not
indicate that the system is about to crash.  However, I have experienced
crashes before, though I'm not sure to what extent such crashes had to do
with this kind of error.  

Actually, I'm on a roll here with 8 days of uptime, but the above messages
seem to be increasing in frequency each day, suggesting that whatever is
causing them is a problem that's becoming more acute over time.  (I'l like
to think I can go for at least 4 weeks without a crash... :-) ) [s/I'l/I'd]
I'm running kernel 2.1.117 on a dual-Pentium II box with Red Hat Linux, release
5.1.

Any advice is much appreciated.

cheers,
Laurence