Date: Tue, 25 Jun 1996 12:12:43 -0400 (EDT) From: Brian Tao <taob@io.org> To: FREEBSD-CURRENT-L <freebsd-current@freebsd.org>, FREEBSD-ISP-L <freebsd-isp@freebsd.org> Subject: New clue to "machine disappears off network" problem? Message-ID: <Pine.NEB.3.92.960625120756.24132E-100000@zap.io.org>
next in thread | raw e-mail | index | archive | help
In another thread, several people noted that they have seen a
machine suddenly lose its Ethernet connection. Most were using an SMC
EtherPower PCI card of some sort, and I think one fellow said he had a
3com. Proposed solutions included pinging the machine from another
node on the network, restarted routed and putting the interface
through an ifconfig down/up cycle.
I upgraded my workstation (the only machine on our network to have
this problem) to 2.2-960612-SNAP, and it started reporting errors on
the network interface:
Jun 25 04:46:26 cabal /kernel: de0: receiver: CRC error
Jun 25 05:29:52 cabal /kernel: de0: receiver: CRC error
Jun 25 05:52:00 cabal /kernel: de0: receiver: CRC error
Jun 25 06:05:25 cabal /kernel: de0: receiver: CRC error
Jun 25 06:18:00 cabal /kernel: de0: receiver: CRC error
Jun 25 06:39:25 cabal /kernel: de0: receiver: CRC error
Jun 25 07:33:37 cabal /kernel: de0: receiver: CRC error
Jun 25 08:03:57 cabal /kernel: de0: receiver: CRC error
[etc.]
No other machines are running this snapshot yet, so I can't say
for sure if there is a correlation between a network hang and the
reporting of these errors. Is this an indication of a bad cable or a
bad card? I would be interested in hearing if anyone else sees these
errors and has experienced the network hang problem.
--
Brian Tao (BT300, taob@io.org, taob@ican.net)
Systems and Network Administrator, Internet Canada Corp.
"Though this be madness, yet there is method in't"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.92.960625120756.24132E-100000>