From owner-freebsd-hackers  Sat Oct 11 10:11:20 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA27864
          for hackers-outgoing; Sat, 11 Oct 1997 10:11:20 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA27859
          for <hackers@freefall.freebsd.org>; Sat, 11 Oct 1997 10:11:15 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id KAA22971;
	Sat, 11 Oct 1997 10:12:23 -0700 (PDT)
Message-Id: <199710111712.KAA22971@implode.root.com>
To: Raul Zighelboim <mango@staff.communique.net>
cc: "'hackers@freefall.freebsd.org'" <hackers@freefall.freebsd.org>
Subject: Re: fxp0 lost connectivity! 
In-reply-to: Your message of "Sat, 11 Oct 1997 11:35:45 CDT."
             <A03CD00C69B1D01195AB00A024ECEB163E0AD0@kaori.communique.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sat, 11 Oct 1997 10:12:23 -0700
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Name  Mtu   Network       Address            Ipkts          Ierrs
>Opkts           Oerrs     Coll
>fxp0  1500  <Link>      00.a0.c9.66.eb.72 925583797 533386 926780807
>2            37893832

   That's a lot of input errors - you should look into that.

>then, last night, the server went down :-(
>Actualy, It did not go down, but the ethernet interface went down.
>Loggin into the console port and doing 'ifconfig fxp0 up' fixed the
>problem.  Otherwise, everything on the system looks alright, and the
>only error found on the log files (I log everything) is a lot of:
>
>xntpd[86]: sendto(204.27.65.10): No route to host
>and similar for other running services...
>
>So: is this a known problem ?

   Yes, it's caused by a hardware bug.

>How do I fix it ?

   There is a fix in both -current and -stable that works around the hardware
bug.

>What should I look at if it happens again (hardly, as I am running
>ifconfig from crontab every */5 now),

   Other than no input coming in, there are no other symptoms.

>Could bad input packets bring the interface down ?

   Yes, the hardware bug is triggered by receiving certain types of garbage.

-DG

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