[vortex-bug] Re: eth1: transmit timed out, tx_status 00 status e000
Aaron Baird
aaron@webcreate.com
Mon, 10 Sep 2001 12:46:25 -0600
This is a multi-part message in MIME format.
------=_NextPart_000_002A_01C139F6.9AC42B50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
I replaced my eth1 (3c905b) card with a LinkSys (LNE100TX) and the error
shown below occurred almost immediately on eth0 (which was a 3c905b). Then,
I replaced eth0 (3c905b) with a LinkSys (LNE100TX) and tested extensively.
I have not received a single error, yet. After working on these issues with
the 3c905b card for weeks and, now, not having a single problem with the
tulip driver in the exact same environment, I am convinced that there is
something wrong with the the 3c59x driver. This is unfortunate because I
really like 3Com network cards.
Aaron
> > Aaron Baird wrote:
> >
> > I have a firewall that is running RedHat 7.1, 2.4.2 kernel, iptables,
> > and two 3com 3c905b network cards. We have a 4 workstation LAN that
> > uses this firewall as the main gateway (and a Cisco router as the
> > actual gateway). About every 24 hours or whenever I do a large,
high-speed, network
> > transfer, I get an error message (shown below) that renders the firewall
useless until I do a reboot
> > (ctl+alt+delete). And the strange thing is, it always occurs on eth1,
never on eth0 (eth1 is connected
> > to a public switch that the router is also connected to).
> >
> > Error Message (from log):
> >
> > Jul 24 13:42:38 castor kernel: NETDEV WATCHDOG: eth1: transmit timed
> > out
> > Jul 24 13:42:38 castor kernel: eth1: transmit timed out, tx_status 00
> > status e000.
> > Jul 24 13:42:38 castor kernel: diagnostics: net 0cda media 8880 dma
> > 000000a0.
> > Jul 24 13:42:38 castor kernel: Flags; bus-master 1, dirty 61401(9)
...
------=_NextPart_000_002A_01C139F6.9AC42B50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D390334018-10092001>I =
replaced my eth1=20
(3c905b) card with a LinkSys (LNE100TX) and the error shown below =
occurred=20
almost immediately on eth0 (which was a 3c905b). Then, I replaced =
eth0=20
(3c905b) with a LinkSys (LNE100TX) and tested extensively. I have =
not=20
received a single error, yet. After working on these issues with =
the=20
3c905b card for weeks and, now, not having a single problem with the =
tulip=20
driver in the exact same environment, I am convinced that there is =
something=20
wrong with the the 3c59x driver. This is unfortunate because I =
really like=20
3Com network cards.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D390334018-10092001></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D390334018-10092001>Aaron</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>> > Aaron Baird wrote: =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > I have a firewall that is =
running RedHat=20
7.1, 2.4.2 kernel, iptables, </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > and two 3com 3c905b network =
cards. We=20
have a 4 workstation LAN that </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > uses this firewall as the =
main gateway=20
(and a Cisco router as the </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > actual gateway). About every =
24 hours or=20
whenever I do a large, high-speed, network </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > transfer, I get an error =
message (shown=20
below) that renders the firewall useless until I do a reboot =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > (ctl+alt+delete). And the =
strange thing=20
is, it always occurs on eth1, never on eth0 (eth1 is connected =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > to a public switch that the =
router is=20
also connected to). </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > Error Message (from log): =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > Jul 24 13:42:38 castor =
kernel: NETDEV=20
WATCHDOG: eth1: transmit timed </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > out </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > Jul 24 13:42:38 castor =
kernel: eth1:=20
transmit timed out, tx_status 00 </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > status e000. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > Jul 24 13:42:38 castor =
kernel:=20
diagnostics: net 0cda media 8880 dma </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > 000000a0. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>> > Jul 24 13:42:38 castor =
kernel: Flags;=20
bus-master 1, dirty 61401(9) </FONT></DIV>
<DIV><SPAN class=3D390334018-10092001><FONT face=3DArial=20
size=3D2>...</FONT></SPAN></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_002A_01C139F6.9AC42B50--