fxp0 Link Going Up And Down

Tim Daneliuk tundra at tundraware.com
Mon Apr 2 21:58:57 UTC 2012


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: <Intel Pro/100 946GZ (ICH7) Network Connection> port 0x1100-0x113f mem 0x90040000-0x90040fff irq 20 at device 8.0 on pci4
miibus0: <MII bus> on fxp0
ukphy0: <Generic IEEE 802.3u media interface> 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 at tundraware.com
>> PGP Key:         http://www.tundraware.com/PGP/
>>
>> _______________________________________________
>> freebsd-questions at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe at freebsd.org"
>>
>>
>
>


-- 
----------------------------------------------------------------------------
Tim Daneliuk     tundra at tundraware.com
PGP Key:         http://www.tundraware.com/PGP/



More information about the freebsd-questions mailing list