From owner-freebsd-isp Tue Jun 25 09:15:12 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA12911 for isp-outgoing; Tue, 25 Jun 1996 09:15:12 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA12898; Tue, 25 Jun 1996 09:15:06 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id MAA21581; Tue, 25 Jun 1996 12:11:48 -0400 (EDT) Date: Tue, 25 Jun 1996 12:12:43 -0400 (EDT) From: Brian Tao To: FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: New clue to "machine disappears off network" problem? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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"