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
[-- Attachment #1 --]
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.
bye Davide
I *could* do that, whats the hostname of your mail server? I'll have it ping that =p 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
-----Original Message-----
From: Julian Elischer [mailto:julian@elischer.org]
Sent: Tuesday, December 05, 2000 2:30 PM
To: Drew J. Weaver
Cc: 'freebsd-net@freebsd.org'
Subject: Re: Really odd problem
> "Drew J. Weaver" wrote:
>
> We have a Freebsd 4.2 box on our network, after the box boots, it
> brings up the network and everything is great, I can telnet into it..
> everything good, but about 30-60 minutes later no incoming traffic is getting
> to the server. If i ping the machine, or telnet to it, I get nothing. If I go
> to the terminal and ping anything then it "wakes up" does anyone have any idea
> what would cause it to stop "listening" to incoming network requests? This is
> becoming very tiresome and i've done everything known to me.
Are you getting messages on the console?
possibly the card is bad and dies after a while..
the transmit timeout for many drivers will try reinitialise the chip.
Which may bring it back to life... (for a while)
you could always add 'ping -i 120 [some address]'
to some startup script
:-)
>
> Thanks,
> -Drew
--
__--_|\ Julian Elischer
/ \ julian@elischer.org
( OZ ) World tour 2000
---> X_.---._/ presently in: Budapest
v
[-- Attachment #2 --]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-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='"MSHTML 4.72.3110.7"' name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2><BR></DIV></FONT>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">
<DIV><FONT face=Arial size=2></FONT><FONT color=#000000 size=2>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.</FONT></DIV>
<DIV><FONT size=2>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.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>bye Davide</FONT></DIV>
<DIV><FONT face=Arial size=2><BR> </DIV></FONT>
<P><FONT size=2>I *could* do that, whats the hostname of your mail server?
I'll have it ping that =p 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</FONT></P>
<P><FONT size=2>-Drew</FONT> </P><BR>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Julian Elischer [<A
href="mailto:julian@elischer.org">mailto:julian@elischer.org</A>]</FONT>
<BR><FONT size=2>Sent: Tuesday, December 05, 2000 2:30 PM</FONT> <BR><FONT
size=2>To: Drew J. Weaver</FONT> <BR><FONT size=2>Cc:
'freebsd-net@freebsd.org'</FONT> <BR><FONT size=2>Subject: Re: Really odd
problem</FONT> </P><BR>
<P><FONT size=2>> "Drew J. Weaver" wrote:</FONT> <BR><FONT
size=2>> </FONT><BR><FONT
size=2>> We
have a Freebsd 4.2 box on our network, after the box boots, it</FONT>
<BR><FONT size=2>> brings up the network and everything is great, I can
telnet into it..</FONT> <BR><FONT size=2>> everything good, but about
30-60 minutes later no incoming traffic is getting</FONT> <BR><FONT
size=2>> to the server. If i ping the machine, or telnet to it, I get
nothing. If I go</FONT> <BR><FONT size=2>> to the terminal and ping
anything then it "wakes up" does anyone have any idea</FONT>
<BR><FONT size=2>> what would cause it to stop "listening" to
incoming network requests? This is</FONT> <BR><FONT size=2>> becoming
very tiresome and i've done everything known to me.</FONT> </P>
<P><FONT size=2>Are you getting messages on the console?</FONT> </P>
<P><FONT size=2>possibly the card is bad and dies after a while..</FONT>
<BR><FONT size=2>the transmit timeout for many drivers will try reinitialise
the chip.</FONT> <BR><FONT size=2>Which may bring it back to life... (for a
while)</FONT> </P>
<P><FONT size=2>you could always add 'ping -i 120 [some address]'
</FONT><BR><FONT size=2>to some startup script </FONT></P>
<P><FONT size=2>:-)</FONT> </P><BR>
<P><FONT size=2>> </FONT><BR><FONT size=2>> Thanks,</FONT> <BR><FONT
size=2>> -Drew</FONT> </P>
<P><FONT size=2>-- </FONT><BR><FONT size=2>
__--_|\ Julian Elischer</FONT> <BR><FONT
size=2> / \
julian@elischer.org</FONT> <BR><FONT size=2> (
OZ ) World tour 2000</FONT> <BR><FONT size=2>--->
X_.---._/ presently in: Budapest</FONT> <BR><FONT
size=2>
v</FONT> </P></BLOCKQUOTE></BODY></HTML>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?023201c06057$7a7541a0$0a01a8c0>