Messages in this thread | | | Date | Tue, 17 Nov 1998 09:51:44 +1000 | From | "Laurence J. Rietberg" <> | Subject | Signs of a kernel about to die? |
| |
Hi there,
Thankyou to those who helped me with my last problem regarding kernel error messages. I am sending another message in the hope that some linux gurus may be able to tell me whether the following dmesg entries are a serious threat to the stability of my system, and/or what I could do to stop these errors arising. Experience has shown that these messages have sometimes preceded a crash, and the messages start to show up more frequently over time (i.e., several days' uptime, preceding a crash).
Here is a uname -a of my system, and some of the dmesgs. Linux lingua.cltr.uq.edu.au 2.1.117 #4 SMP Fri Aug 21 13:44:57 EST 1998 i686 unknown Uptime:9:49am up 6 days Release: Linux 5.1 (Manhattan) Some dmesgs: TCPv4 bad checksum from 210.157.0.13:0050 to 130.102.224.1:082c, len=1367/1367/1387 TCPv4 bad checksum from 202.219.63.99:0050 to 130.102.224.1:08bb, len=20/20/40 TCPv4 bad checksum from 200.241.125.143:0894 to 130.102.224.1:1f40, len=20/20/40TCPv4 bad checksum from 202.155.2.226:5bd9 to 130.102.224.1:1f40, len=20/20/40 TCPv4 bad checksum from 202.155.2.226:5bda to 130.102.224.1:1f40, len=20/20/40 TCPv4 bad checksum from 202.155.2.226:5bdb to 130.102.224.1:1f40, len=20/20/40 TCPv4 bad checksum from 172.22.14.37:07b1 to 130.102.224.1:0017, len=21/21/41 TCPv4 bad checksum from 172.22.14.37:07a1 to 130.102.224.1:0017, len=20/20/40 TCPv4 bad checksum from 194.85.166.39:0ab4 to 130.102.224.1:0050, len=407/407/427 TCPv4 bad checksum from 210.157.0.13:0050 to 130.102.224.1:0bb8, len=1480/1480/1500 Socket destroy delayed (r=0 w=1632) TCPv4 bad checksum from 210.157.0.16:0050 to 130.102.224.1:0fe4, len=1480/1480/1500 TCPv4 bad checksum from 169.139.185.8:0d29 to 130.102.224.1:1f40, len=32/32/52 TCPv4 bad checksum from 128.135.177.92:0618 to 130.102.224.1:1f40, len=284/284/304 TCPv4 bad checksum from 128.135.177.92:0619 to 130.102.224.1:1f40, len=289/289/309 Socket destroy delayed (r=0 w=160)
Please reply to me email address, rather than the linux-kernel list, as I am not on the linux-kernel list.
Thankyou in advance for your advice. Laurence (SysAdmin, UQ)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |