summaryrefslogtreecommitdiffstats
path: root/crypto/openssh/ssh-keygen.1
diff options
context:
space:
mode:
authorwpaul <wpaul@FreeBSD.org>2003-07-11 08:19:52 +0000
committerwpaul <wpaul@FreeBSD.org>2003-07-11 08:19:52 +0000
commit4d41e2d69fdd3612c75d5889cc640a08728bfad8 (patch)
treec210d9f040a926c7e906b9da69c7b5577b9a32c5 /crypto/openssh/ssh-keygen.1
parentfd945a32e8edfd0780990850ebe8b4c598275529 (diff)
downloadFreeBSD-src-4d41e2d69fdd3612c75d5889cc640a08728bfad8.zip
FreeBSD-src-4d41e2d69fdd3612c75d5889cc640a08728bfad8.tar.gz
Squelch spurious "gigabit link up" messages generated on some fiber NICs
(mainly the 3Com 3c996B/BCM5701). For some reason that I don't fully understand, the 5701 signals PCS encoding errors as though they were link change events, i.e. the 'link state changed' bit in the status word of the status block is updated and an interrupt is generated. This would cause the bge_tick() function to be invoked and a "gigabit link up" message to be printed on the console. To avoid this, the interrupt handler now checks the MAC status register when a link change interrupt is triggered, and it will only call the bge_tick() function if the 'PCS encoding error detected' bit is clear. (This change should have no effect on copper NICs since this bit can only ever be set in TBI mode. I do not know how it affects 5704 NICs with a BCM8002 SERDES PHY.) Special thanks to: Sherry Rogers at UCB for allowing me access to one of their traffic monitor boxes so I could diagnose this problem.
Diffstat (limited to 'crypto/openssh/ssh-keygen.1')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud