Messages in this thread |  | | | From | aidas@ixsrs4 ... | | Date | Sat, 22 Feb 1997 09:43:46 -0600 (CST) | | Subject | Re: TCPv4 errors | |
On Sat, 22 Feb 1997, Laslo Orto wrote:
> I installed linux (slackware 3.1 with kernel 2.1.25) and i'm geting TCPv4
> bad checksum errors on the console (a lot of them). The network card is
> Realtek (ne2000)
> here is output from dmesg:
> TCPv4 bad checksum from 42065ac2:008b to 0b7396cd:07a0, len=532/532/552
> TCPv4 bad checksum from 42065ac2:008b to 0b7396cd:07a0, len=532/532/552
> TCPv4 bad checksum from 42065ac2:008b to 0b7396cd:07a0, len=532/532/552
> TCPv4 bad checksum from 42065ac2:008b to 0b7396cd:07a0, len=532/532/552
These are just debugging messages. If you don't like them, go to a
non-development kernel, or run 'dmesg -n 1' which will force all non
KERN_EMERG messages to go to the syslog only.
--
"Things fall apart; the centre cannot hold. Mere anarchy is loosed upon the
world; The blood-dimmed tide is loosed, and everywhere the ceremony of
innocence is drowned; The best lack all conviction, while the worst are full
of passionate intensity." -- "Second Coming" by Yeats.
|  |