From owner-freebsd-questions@FreeBSD.ORG Fri Aug 15 16:38:53 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 646691065676 for ; Fri, 15 Aug 2008 16:38:49 +0000 (UTC) (envelope-from pprocacci@datapipe.com) Received: from fmailhost04.isp.att.net (fmailhost04.isp.att.net [204.127.217.104]) by mx1.freebsd.org (Postfix) with ESMTP id 2E1C58FC25 for ; Fri, 15 Aug 2008 16:38:49 +0000 (UTC) (envelope-from pprocacci@datapipe.com) Received: from [10.5.21.122] (adsl-241-169-57.bna.bellsouth.net[74.241.169.57]) by isp.att.net (frfwmhc04) with ESMTP id <20080815163848H040096lpge>; Fri, 15 Aug 2008 16:38:48 +0000 X-Originating-IP: [74.241.169.57] Message-ID: <48A5B106.2040201@datapipe.com> Date: Fri, 15 Aug 2008 11:38:30 -0500 From: Paul Procacci User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Jos Chrispijn References: <48A5AB9F.1070001@webrz.net> In-Reply-To: <48A5AB9F.1070001@webrz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions Subject: Re: Up_down~up X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Aug 2008 16:38:54 -0000 Jos Chrispijn wrote: > Just saw this in my security log: > > +++ /tmp/security.CVzQ19kE 2008-08-15 00:04:29.000000000 +0200 > +fxp0: link state changed to DOWN > +fxp0: link state changed to UP > +fxp0: link state changed to DOWN > +fxp0: link state changed to UP > +fxp0: link state changed to DOWN > +fxp0: link state changed to UP > > Does this indicate a nearly_broken nic or is this caused by someting > else? > Jos > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" I've seen this with a bad cat5 cable a couple of times. ~Paul