RES: eth0: Transmit error

Cleber P. de Souza cleber.souza at cmp.ind.br
Fri Sep 3 13:43:42 UTC 2004


Is this NIC to a HUB or a Switch?
When I was using my NIC conected to a HUB and all of a sudden i got this
messages at the /var/log/messages, all the peers connected are flooded with
ICMP.
I solve this replace the HUB by another.
Iwas using a 3COM NIC.

In teory, this problem could be due the HUB versus Switch characteristics
where the HUB don't can hear and transmit at the same time.

***
Cleber P. de Souza

-----Mensagem original-----
De: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com]
Em nome de Margaret Doll
Enviada em: sexta-feira, 3 de setembro de 2004 10:18
Para: Redhat-list at redhat.com
Assunto: Fwd: eth0: Transmit error

from  http://www.scyld.com/vortex.html

0x82
Out of window collision.  This typically occurs when some other Ethernet
host is incorrectly set to full duplex on a half duplex network.

We are getting hit by another computer on our network.  The error messages
are

nnn.nnn.nnn.nnn  ( on our local subnet)  sent an invalid ICMP type 11, code
0 error to a broadcast: ...:  551Time(s)

Now we have to hunt down the "stray" computer.  School is starting; problems
come in with the students.

Begin forwarded message:

> From: Margaret Doll <Margaret_Doll at brown.edu>
> Date: Thu Sep 2, 2004  10:52:29 AM US/Eastern
> To: redhat-list at redhat.com
> Subject: eth0: Transmit error
>
> Does anyone know why this would start happening to a system?  The 
> system was running Rh 9.0.  I upgraded it to RH Enterprise ES 3 a week 
> ago Wednesday.
>
> Sep  2 10:46:45 server kernel: eth0: Transmit error, Tx status 
> register 82.
> Sep  2 10:46:45 server kernel: Probably a duplex mismatch.  See 
> Documentation/networking/vorte x.txt
> Sep  2 10:46:45 server kernel:   Flags; bus-master 1, dirty 32019(3) 
> current 32019(3)
> Sep  2 10:46:45 server kernel:   Transmit list 00000000 vs. cf09c2c0.
> Sep  2 10:46:45 server kernel:   0: @cf09c200  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   1: @cf09c240  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   2: @cf09c280  length 800005ea status 
> 800105ea
> Sep  2 10:46:45 server kernel:   3: @cf09c2c0  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   4: @cf09c300  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   5: @cf09c340  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   6: @cf09c380  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   7: @cf09c3c0  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   8: @cf09c400  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   9: @cf09c440  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   10: @cf09c480  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   11: @cf09c4c0  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   12: @cf09c500  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   13: @cf09c540  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   14: @cf09c580  length 800005ea status 
> 000105ea
> Sep  2 10:46:45 server kernel:   15: @cf09c5c0  length 800005ea status 
> 000105ea
>
>
> Thanks
>
-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list





More information about the redhat-list mailing list