From owner-freebsd-current  Tue Jun 25 09:29:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA14268
          for current-outgoing; Tue, 25 Jun 1996 09:29:31 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA14249;
          Tue, 25 Jun 1996 09:29:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id JAA10524; Tue, 25 Jun 1996 09:29:09 -0700 (PDT)
Message-Id: <199606251629.JAA10524@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Brian Tao <taob@io.org>
cc: FREEBSD-CURRENT-L <freebsd-current@freebsd.org>,
        FREEBSD-ISP-L <freebsd-isp@freebsd.org>
Subject: Re: New clue to "machine disappears off network" problem? 
In-reply-to: Your message of "Tue, 25 Jun 1996 12:12:43 EDT."
             <Pine.NEB.3.92.960625120756.24132E-100000@zap.io.org> 
From: David Greenman <davidg@root.com>
Reply-To: davidg@root.com
Date: Tue, 25 Jun 1996 09:29:09 -0700
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>    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.

   It appears to be caused by a bug in the driver. It has been seen on several
other machines as well (not the least of which was wcarchive before I pulled
out the driver and put the old one back in). The author is at the IETF meeting
and will be back next week.
   There is also a bug in it that will cause a panic. It'll be fixed after
2.1.5R ships.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project