Linux-kernel mailing list archive 1998-42,: Re: 2.1.126-2-ac1: Local: Corrupted check bytes on input.

# Re: 2.1.126-2-ac1: Local: Corrupted check bytes on input.

Gregory Maxwell (linker@z.ml.org)
Sun, 18 Oct 1998 18:12:56 -0400 (EDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Gregory Maxwell: "Re: 2.1.126-2-ac1: Local: Corrupted check bytes on input."
- Previous message: Andries.Brouwer@cwi.nl: "Re: bug introduced in 2.0.34"
- In reply to: Alan Cox: "Re: 2.1.126-2-ac1: Local: Corrupted check bytes on input."

On Sun, 18 Oct 1998, Alan Cox wrote:

> > I've been running 2.1.126-2-ac1 on my Dual 166 and have been expirencing:
> > Local: Corrupted check bytes on input.
> > When slogined to a 2.0.35 box over a IP masqed ISDN line. I was ona VT.. I
> > believe it started with .124 but perhaps it was .125..
>
> What architecture - Russ King (the arm linux god) reported this with 2.1.12x
> on the ARM changing bytes to 0xFF occasionally

x86. First on my Dual-166MMX then on a Celron 300a in a BX board. NO
OVERCLOCKING TAKING PLACE. EVER. :)

I didn't report it on my dual166mmx because the kernel is compiled with
pgcc.

On the 300a it's a fairly stock RH5.1 computer and the problem only
started after I moved from 2.0.35.

Everything else seems fine.
It's only during a slogin too..
> > Now it too is getting this error while slogined (it kills my ssh connect
> > too) .. This in under X..
>
> Sounds like something is causing memory corruptions.
>
> Any other people with the same errors (note not tcp checksum errors)
>
> Alan

-
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/

- Next message: Gregory Maxwell: "Re: 2.1.126-2-ac1: Local: Corrupted check bytes on input."
- Previous message: Andries.Brouwer@cwi.nl: "Re: bug introduced in 2.0.34"
- In reply to: Alan Cox: "Re: 2.1.126-2-ac1: Local: Corrupted check bytes on input."