From owner-freebsd-questions@FreeBSD.ORG Mon Apr 2 21:58:57 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B34041065688 for ; Mon, 2 Apr 2012 21:58:57 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 8240E8FC14 for ; Mon, 2 Apr 2012 21:58:57 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.5/8.14.5) with ESMTP id q32LweEh037466 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 2 Apr 2012 16:58:40 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <4F7A210F.4060800@tundraware.com> Date: Mon, 02 Apr 2012 16:58:39 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120310 Thunderbird/11.0 MIME-Version: 1.0 To: FreeBSD Mailing List References: <4F78B8DB.1090508@tundraware.com> <4F7A117B.8050907@sentex.net> In-Reply-To: <4F7A117B.8050907@sentex.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ozzie.tundraware.com [192.168.0.1]); Mon, 02 Apr 2012 16:58:40 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: q32LweEh037466 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: fxp0 Link Going Up And Down 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: Mon, 02 Apr 2012 21:58:57 -0000 On 04/02/2012 03:52 PM, Mike Tancsa wrote: > On 4/1/2012 4:21 PM, Tim Daneliuk wrote: >> I am seeing this intermittently: >> >> Apr 1 14:48:36 host kernel: fxp0: link state changed to DOWN >> Apr 1 14:52:27 host kernel: fxp0: link state changed to UP > > There were some fixes to the fxp driver on ~ March 26th that fixed the > NIC bouncing up and down when it went into promisc mode. But those > bounces were very short lived (a few seconds to transition). Your > up/down events are minutes. Perhaps the cable modem is going into some > sort of "sleep mode" ? Or perhaps just a hardware issue. If you can, I don't think so. The modem has a built in hub and I am not observing this problem on other devices plug in there. > try and put a simple hub or switch between the cable modem and your NIC > and see if you still get bounces. > > Also, there are many variants of fxp hardware. Post the output of > > egrep -i "fxp|phy" /var/run/dmesg.boot > fxp0: port 0x1100-0x113f mem 0x90040000-0x90040fff irq 20 at device 8.0 on pci4 miibus0: on fxp0 ukphy0: PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow fxp0: Ethernet address: ... fxp0: [ITHREAD] > and > > sysctl -a dev.fxp dev.fxp.0.%desc: Intel Pro/100 946GZ (ICH7) Network Connection dev.fxp.0.%driver: fxp dev.fxp.0.%location: slot=8 function=0 dev.fxp.0.%pnpinfo: vendor=0x8086 device=0x1094 subvendor=0x8086 subdevice=0x0001 class=0x020000 dev.fxp.0.%parent: pci4 dev.fxp.0.int_delay: 1000 dev.fxp.0.bundle_max: 6 dev.fxp.0.rnr: 0 dev.fxp.0.stats.rx.good_frames: 2004295 dev.fxp.0.stats.rx.crc_errors: 0 dev.fxp.0.stats.rx.alignment_errors: 0 dev.fxp.0.stats.rx.rnr_errors: 0 dev.fxp.0.stats.rx.overrun_errors: 0 dev.fxp.0.stats.rx.cdt_errors: 0 dev.fxp.0.stats.rx.shortframes: 0 dev.fxp.0.stats.rx.pause: 0 dev.fxp.0.stats.rx.controls: 0 dev.fxp.0.stats.rx.tco: 0 dev.fxp.0.stats.tx.good_frames: 1701132 dev.fxp.0.stats.tx.maxcols: 0 dev.fxp.0.stats.tx.latecols: 0 dev.fxp.0.stats.tx.underruns: 0 dev.fxp.0.stats.tx.lostcrs: 0 dev.fxp.0.stats.tx.deffered: 0 dev.fxp.0.stats.tx.single_collisions: 0 dev.fxp.0.stats.tx.multiple_collisions: 0 dev.fxp.0.stats.tx.total_collisions: 0 dev.fxp.0.stats.tx.pause: 0 dev.fxp.0.stats.tx.tco: 0 Thanks for taking time to look into this... > > ---Mike > >> >> This is observed both on some 8.2-STABLE and 8.3-PRERELEASE versions >> on the same server. I have replaced the ethernet cable as well as the >> device on the other end (a cable internet box), but the problem >> intermittently persists. It appears not to be a mechanical issue >> insofar as I can wiggle the cable at each end and not introduce this >> problem. >> >> fxp0 in this case is the on-board NIC of an Intel mobo. >> >> Ideas anyone? >> ---------------------------------------------------------------------------- >> >> Tim Daneliuk tundra@tundraware.com >> PGP Key: http://www.tundraware.com/PGP/ >> >> _______________________________________________ >> 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" >> >> > > -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/