[eepro100] eth0: Transmit timed out: status f048 0000 at 1614128871/1614128899 command 000ca000.
Amrik Singh
asingh@exscape.net
Thu Mar 21 19:55:00 2002
This is a multi-part message in MIME format.
------=_NextPart_000_08F8_01C1D112.AA103550
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thanks for the reply.
I'm begining to think if I should force it to stay at 100mbits full =
duplex via option=3D0x30 i believe. We have changed to all the =
different intel 10/100s we had.. we still see this problem.
Point to be noted though. These cards were also used in our fbsd =
machines.. where they passed close to 100mbits to peaks and for very =
long time. I don't know what could be causing it to mess up in linux. =
When I tried the 3com 10/100, same thing as well (i think it was 905B.. =
). They only worked for 3 days and then the system timed out with =
them.. intel cards seem to last longer before they timeout. Various =
3com cards were put in as part of trouble shooting method.. including =
various things from module driver to statically linked.. including =
changing the switches.. to cat5 cabling.. and we're still having that. =
However, another point to be noted. Switches are on Nway.. so they =
negotiate to 100mbits full duplex with the card. Could it be this ? (we =
haven't tested this yet and is the only thing we haven't tested)
My thinking on this is.. they crap out and eth0 is not able to negotiate =
100mbits after passing large amount of data. I think my solution may be =
to force 100mbits in full duplex mode. However, I would like to know =
what your input on this... because we can not test this in a live server =
environment.
Amrik
Amrik,
I had a similar problem... not sure if it was really the driver or the =
network traffic. I was running Samba and a VPRN router (Nortel Shasta) =
was responding with a ICMP broadcast error about every 3-5 min. Still =
not sure what the problem was, as I just shutdown smb. This is not the =
ideal solution I was looking for, as I use samba quite a bit. But I do =
see these timeout messages similar to what you have here. I'm certain =
there is something on the network related to the problem, but I've not =
had time to track it down yet. Hope this helps.
j d wilson
-----Original Message-----
From: Amrik Singh [mailto:asingh@exscape.net]
Sent: Thursday, March 21, 2002 18:50
To: eepro100@scyld.com
Subject: [eepro100] eth0: Transmit timed out: status f048 0000 at =
1614128871/1614128899 command 000ca000.
We're hosting this dual 1ghz.. w/1gb of ram with smp kernel.
2.4.7-10smp #1 SMP Thu Sep 6 17:09:31 EDT 2001 i686 unknown
Every week, it crashes.. as it can pull/push upto 50mbits/s and then =
we have to reboot to fix the issue.
Please help me. This thing also did with other 3com 10/100 nic we =
put in. Thing to be noted is.. all of them on auto select as far as =
speed... so i'm wondering perhaps that Nway messes it up and it needs to =
be set manually to 100mbits full duplex ?
here is other useful info.
Mar 21 12:23:10 server kernel: NETDEV WATCHDOG: eth0: transmit timed =
out
Mar 21 12:23:10 server kernel: eth0: Transmit timed out: status f048 =
0000 at 1614128871/1614128899 command 000ca000.
Mar 21 12:23:14 server kernel: NETDEV WATCHDOG: eth0: transmit timed =
out
Mar 21 12:23:14 server kernel: eth0: Transmit timed out: status f048 =
0000 at 1614128899/1614128929 command 0001a000.
Mar 21 12:23:18 server kernel: NETDEV WATCHDOG: eth0: transmit timed =
out
Mar 21 12:23:18 server kernel: eth0: Transmit timed out: status f048 =
0000 at 1614128929/1614128959 command 0001a000.
Mar 21 12:23:22 server kernel: NETDEV WATCHDOG: eth0: transmit timed =
out
Mar 21 12:23:22 server kernel: eth0: Transmit timed out: status f048 =
0000 at 1614128959/1614128989 command 0001a000.
lsmod
Module Size Used by
autofs 12068 0 (autoclean) (unused)
eepro100 18128 1
ext3 67728 2
jbd 44480 2 [ext3]
[root@server progs-corey]# ./pci-config
pci-config.c:v2.02 1/8/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Device #1 at bus 0 device/function 0/0, 06911106.
Device #2 at bus 0 device/function 1/0, 85981106.
Device #3 at bus 0 device/function 7/0, 06861106.
Device #4 at bus 0 device/function 7/1, 05711106.
Device #5 at bus 0 device/function 7/4, 30571106.
Device #6 at bus 0 device/function 9/0, 8a015333.
Device #7 at bus 0 device/function 11/0, 12298086.
Thanks
Amrik Singh
eXscape Communications Inc.
------=_NextPart_000_08F8_01C1D112.AA103550
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=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Thanks for the reply.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I'm begining to think if I should force =
it to stay=20
at 100mbits full duplex via option=3D0x30 i believe. We have =
changed to all=20
the different intel 10/100s we had.. we still see this =
problem.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Point to be noted though. These =
cards were=20
also used in our fbsd machines.. where they passed close to 100mbits to =
peaks=20
and for very long time. I don't know what could be causing it to =
mess up=20
in linux. When I tried the 3com 10/100, same thing as well (i =
think=20
it was 905B.. ). They only worked for 3 days and then the system =
timed out=20
with them.. intel cards seem to last longer before they =
timeout. =20
Various 3com cards were put in as part of trouble shooting method.. =
including=20
various things from module driver to statically linked.. including =
changing the=20
switches.. to cat5 cabling.. and we're still having that. However, =
another=20
point to be noted. Switches are on Nway.. so they negotiate to =
100mbits=20
full duplex with the card. Could it be this ? (we haven't tested =
this yet=20
and is the only thing we haven't tested)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My thinking on this is.. they crap out =
and eth0 is=20
not able to negotiate 100mbits after passing large amount of data. =
I think=20
my solution may be to force 100mbits in full duplex mode. However, =
I would=20
like to know what your input on this... because we can not test this in =
a live=20
server environment.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Amrik</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV><FONT face=3DArial size=3D2></FONT><BR></DIV>
<DIV><SPAN class=3D623482922-21032002><FONT face=3DVerdana =
color=3D#0000ff=20
size=3D2>Amrik,</FONT></SPAN></DIV>
<DIV><SPAN class=3D623482922-21032002><FONT face=3DVerdana =
color=3D#0000ff size=3D2>I=20
had a similar problem... not sure if it was really the driver or the =
network=20
traffic. I was running Samba and a VPRN router (Nortel Shasta) =
was=20
responding with a ICMP broadcast error about every 3-5 min. =
Still not=20
sure what the problem was, as I just shutdown smb. This is not =
the ideal=20
solution I was looking for, as I use samba quite a bit. But I do =
see=20
these timeout messages similar to what you have here. I'm =
certain there=20
is something on the network related to the problem, but I've not had =
time to=20
track it down yet. Hope this helps.</FONT></SPAN></DIV>
<DIV><SPAN class=3D623482922-21032002><FONT face=3DVerdana =
color=3D#0000ff size=3D2>j=20
d wilson</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Amrik Singh=20
[mailto:asingh@exscape.net]<BR><B>Sent:</B> Thursday, March 21, 2002 =
18:50<BR><B>To:</B> eepro100@scyld.com<BR><B>Subject:</B> [eepro100] =
eth0:=20
Transmit timed out: status f048 0000 at 1614128871/1614128899 =
command=20
000ca000.<BR><BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>We're hosting this dual 1ghz.. =
w/1gb of ram=20
with smp kernel.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2.4.7-10smp #1 SMP Thu Sep 6 =
17:09:31 EDT 2001=20
i686 unknown<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Every week, it crashes.. as it can =
pull/push=20
upto 50mbits/s and then we have to reboot to fix the =
issue.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Please help me. This thing =
also did with=20
other 3com 10/100 nic we put in. Thing to be noted is.. all of =
them on=20
auto select as far as speed... so i'm wondering perhaps that Nway =
messes it=20
up and it needs to be set manually to 100mbits full duplex =
?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>here is other useful =
info.</DIV></FONT>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Mar 21 12:23:10 server kernel: =
NETDEV WATCHDOG:=20
eth0: transmit timed out<BR>Mar 21 12:23:10 server kernel: eth0: =
Transmit=20
timed out: status f048 0000 at 1614128871/1614128899 command=20
000ca000.<BR>Mar 21 12:23:14 server kernel: NETDEV WATCHDOG: eth0: =
transmit=20
timed out<BR>Mar 21 12:23:14 server kernel: eth0: Transmit timed =
out: status=20
f048 0000 at 1614128899/1614128929 command 0001a000.<BR>Mar 21 =
12:23:18 server kernel: NETDEV WATCHDOG: eth0: transmit timed =
out<BR>Mar 21=20
12:23:18 server kernel: eth0: Transmit timed out: status f048 =
0000 at=20
1614128929/1614128959 command 0001a000.<BR>Mar 21 12:23:22 server =
kernel:=20
NETDEV WATCHDOG: eth0: transmit timed out<BR>Mar 21 12:23:22 server =
kernel:=20
eth0: Transmit timed out: status f048 0000 at =
1614128959/1614128989=20
command 0001a000.<BR></DIV></FONT>
<DIV><FONT face=3DArial size=3D2>lsmod</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial=20
=
size=3D2>Module &nbs=
p; =20
Size Used=20
=
by<BR>autofs &=
nbsp; =20
12068 0 (autoclean)=20
=
(unused)<BR>eepro100  =
; =20
18128 =20
=
1<BR>ext3 &nbs=
p; =20
67728 =20
=
2<BR>jbd  =
; =20
44480 2 [ext3]<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>[root@server progs-corey]#=20
./pci-config<BR>pci-config.c:v2.02 1/8/2001 Donald Becker (<A=20
href=3D"mailto:becker@scyld.com">becker@scyld.com</A>)<BR> <A=20
=
href=3D"http://www.scyld.com/diag/index.html">http://www.scyld.com/diag/i=
ndex.html</A><BR>Device=20
#1 at bus 0 device/function 0/0, 06911106.<BR>Device #2 at bus 0=20
device/function 1/0, 85981106.<BR>Device #3 at bus 0 device/function =
7/0,=20
06861106.<BR>Device #4 at bus 0 device/function 7/1, =
05711106.</FONT><FONT=20
face=3DArial size=3D2><BR>Device #5 at bus 0 device/function 7/4,=20
30571106.<BR>Device #6 at bus 0 device/function 9/0, =
8a015333.<BR>Device #7=20
at bus 0 device/function 11/0, 12298086.<BR></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Amrik Singh</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>eXscape Communications =
Inc.</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> </DIV></BLOCKQUOTE></BLOCKQUOTE></FONT></BODY></HTML>
------=_NextPart_000_08F8_01C1D112.AA103550--