Date: Thu, 7 Dec 2000 15:10:39 +0100 From: "Davide Lemma" <davide.lemma@sito.it> To: <freebsd-net@freebsd.org> Subject: Re: Really odd problem Message-ID: <023201c06057$7a7541a0$0a01a8c0@dado.gruppoidea.it>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
------=_NextPart_000_022F_01C0605F.DBFFADE0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I had the same problem... my server was an ADM-II K6-400, the =
motherboard was a SOYO and 3Com50X as ethernet card, by now the problem =
is solved by changing the motherboard and the case.
For my personal opinion it is something linked to the APM, or some =
strange bug in the motherboard's chipset, not the nic card... because =
now it works right.
=20
bye Davide
=20
=20
I *could* do that, whats the hostname of your mail server? I'll have =
it ping that =3Dp No messages on the console at all, and again i've =
tried two seperate NIC cards both the (onboard intel) and the offboard =
PCI Intel 10/100
-Drew=20
=20
=20
-----Original Message-----=20
From: Julian Elischer [mailto:julian@elischer.org]=20
Sent: Tuesday, December 05, 2000 2:30 PM=20
To: Drew J. Weaver=20
Cc: 'freebsd-net@freebsd.org'=20
Subject: Re: Really odd problem=20
=20
=20
> "Drew J. Weaver" wrote:=20
>=20
> We have a Freebsd 4.2 box on our network, after the box =
boots, it=20
> brings up the network and everything is great, I can telnet into =
it..=20
> everything good, but about 30-60 minutes later no incoming traffic =
is getting=20
> to the server. If i ping the machine, or telnet to it, I get =
nothing. If I go=20
> to the terminal and ping anything then it "wakes up" does anyone =
have any idea=20
> what would cause it to stop "listening" to incoming network =
requests? This is=20
> becoming very tiresome and i've done everything known to me.=20
Are you getting messages on the console?=20
possibly the card is bad and dies after a while..=20
the transmit timeout for many drivers will try reinitialise the =
chip.=20
Which may bring it back to life... (for a while)=20
you could always add 'ping -i 120 [some address]'=20
to some startup script =20
:-)=20
=20
=20
>=20
> Thanks,=20
> -Drew=20
--=20
__--_|\ Julian Elischer=20
/ \ julian@elischer.org=20
( OZ ) World tour 2000=20
---> X_.---._/ presently in: Budapest=20
v=20
------=_NextPart_000_022F_01C0605F.DBFFADE0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><TITLE>RE: Really odd problem</TITLE><!DOCTYPE =
HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD =
HTML 3.2//EN">
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><BR></DIV></FONT>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
<DIV><FONT face=3DArial size=3D2></FONT><FONT color=3D#000000 =
size=3D2>I had the=20
same problem... my server was an ADM-II K6-400, the motherboard was =
a SOYO=20
and 3Com50X as ethernet card, by now the problem is solved by =
changing the=20
motherboard and the case.</FONT></DIV>
<DIV><FONT size=3D2>For my personal opinion it is something linked =
to the APM,=20
or some strange bug in the motherboard's chipset, not the nic =
card...=20
because now it works right.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>bye Davide</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR> </DIV></FONT>
<P><FONT size=3D2>I *could* do that, whats the hostname of your mail =
server?=20
I'll have it ping that =3Dp No messages on the console at all, and =
again i've=20
tried two seperate NIC cards both the (onboard intel) and the =
offboard PCI=20
Intel 10/100</FONT></P>
<P><FONT size=3D2>-Drew</FONT> </P><BR>
<P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From:=20
Julian Elischer [<A=20
=
href=3D"mailto:julian@elischer.org">mailto:julian@elischer.org</A>]</FONT=
>=20
<BR><FONT size=3D2>Sent: Tuesday, December 05, 2000 2:30 PM</FONT> =
<BR><FONT=20
size=3D2>To: Drew J. Weaver</FONT> <BR><FONT size=3D2>Cc:=20
'freebsd-net@freebsd.org'</FONT> <BR><FONT size=3D2>Subject: Re: =
Really odd=20
problem</FONT> </P><BR>
<P><FONT size=3D2>> "Drew J. Weaver" wrote:</FONT> =
<BR><FONT=20
size=3D2>> </FONT><BR><FONT=20
=
size=3D2>> =
We=20
have a Freebsd 4.2 box on our network, after the box boots, =
it</FONT>=20
<BR><FONT size=3D2>> brings up the network and everything is =
great, I can=20
telnet into it..</FONT> <BR><FONT size=3D2>> everything good, but =
about=20
30-60 minutes later no incoming traffic is getting</FONT> <BR><FONT=20
size=3D2>> to the server. If i ping the machine, or telnet to it, =
I get=20
nothing. If I go</FONT> <BR><FONT size=3D2>> to the terminal and =
ping=20
anything then it "wakes up" does anyone have any =
idea</FONT>=20
<BR><FONT size=3D2>> what would cause it to stop =
"listening" to=20
incoming network requests? This is</FONT> <BR><FONT size=3D2>> =
becoming=20
very tiresome and i've done everything known to me.</FONT> </P>
<P><FONT size=3D2>Are you getting messages on the console?</FONT> =
</P>
<P><FONT size=3D2>possibly the card is bad and dies after a =
while..</FONT>=20
<BR><FONT size=3D2>the transmit timeout for many drivers will try =
reinitialise=20
the chip.</FONT> <BR><FONT size=3D2>Which may bring it back to =
life... (for a=20
while)</FONT> </P>
<P><FONT size=3D2>you could always add 'ping -i 120 [some address]'=20
</FONT><BR><FONT size=3D2>to some startup script </FONT></P>
<P><FONT size=3D2>:-)</FONT> </P><BR>
<P><FONT size=3D2>> </FONT><BR><FONT size=3D2>> Thanks,</FONT> =
<BR><FONT=20
size=3D2>> -Drew</FONT> </P>
<P><FONT size=3D2>-- </FONT><BR><FONT =
size=3D2> =20
__--_|\ Julian Elischer</FONT> <BR><FONT=20
size=3D2> =
/ \=20
julian@elischer.org</FONT> <BR><FONT size=3D2> =
( =20
OZ ) World tour 2000</FONT> <BR><FONT =
size=3D2>--->=20
X_.---._/ presently in: Budapest</FONT> <BR><FONT=20
=
size=3D2> &nbs=
p;=20
v</FONT> </P></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_022F_01C0605F.DBFFADE0--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?023201c06057$7a7541a0$0a01a8c0>