Messages in this thread |  | | | From | (H.J. Lu) | | Subject | Re: Massive TCPv4 bad checksum | | Date | Sun, 18 Oct 1998 08:36:51 -0700 (PDT) |
| |
> > > > 2.0 just never spat out a message when it got a bad checksum, so this is > > > probably why you never saw it before. If you're noticing that there's an > > > actual packet data problem that didn't exist before with 2.0, then you > > > might want to investigate. The message will be probably be removed by > > > 2.2. > > > > > > > I can tell my SLIP speed is slower than 2.0 and there are quite > > some corrupted packets come over SLIP link. > > Are you running an SMP kernel on a uniprocessor machine, what disk IO > and what other major devices. >
It is running SMP on a SMP machine, which is all SCSI machine connected to BusLogic 958. It has a Tulip network card. It doesn't run X. One thing I didn't mention. I am not sure if it is related. Since I upgraded to 2.1, I need several tries to setup my CSLIP link. Sometimes, the link will die immediately when the connection is made. Sometimes, the line is connected, but ping doesn't respond. I have to bring the link down and try again.
BTW, 2.0 seems ok on the same machine.
-- H.J. Lu (hjl@gnu.org)
- 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/
|  |