diff options
| author | yongari <yongari@FreeBSD.org> | 2009-11-06 18:51:05 +0000 |
|---|---|---|
| committer | yongari <yongari@FreeBSD.org> | 2009-11-06 18:51:05 +0000 |
| commit | bee1d701e2e2991fc5d1ba3049fbf0ccf7d39a47 (patch) | |
| tree | 11b74625524dc38429f19212c5f15024b557b336 /sys/dev/msk/if_msk.c | |
| parent | 09931cab3a4471b034b4e83f6222e97a4ceb6c5b (diff) | |
| download | FreeBSD-src-bee1d701e2e2991fc5d1ba3049fbf0ccf7d39a47.zip FreeBSD-src-bee1d701e2e2991fc5d1ba3049fbf0ccf7d39a47.tar.gz | |
It's normal to see Rx FIFO overruns under high network load and
showing the message creates other side-effects. Remove the Rx
FIFO overrun message in interrupt handler. msk(4) should recover
from the FIFO overruns without any user intervention. Users can
still check the Rx FIFO overrun counter from MAC MIB statistics
maintained in driver(dev.msk.0.stats.rx.overflows).
Diffstat (limited to 'sys/dev/msk/if_msk.c')
| -rw-r--r-- | sys/dev/msk/if_msk.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/sys/dev/msk/if_msk.c b/sys/dev/msk/if_msk.c index cdb65b6..061d8c7 100644 --- a/sys/dev/msk/if_msk.c +++ b/sys/dev/msk/if_msk.c @@ -3217,11 +3217,9 @@ msk_intr_gmac(struct msk_if_softc *sc_if) status = CSR_READ_1(sc, MR_ADDR(sc_if->msk_port, GMAC_IRQ_SRC)); /* GMAC Rx FIFO overrun. */ - if ((status & GM_IS_RX_FF_OR) != 0) { + if ((status & GM_IS_RX_FF_OR) != 0) CSR_WRITE_4(sc, MR_ADDR(sc_if->msk_port, RX_GMF_CTRL_T), GMF_CLI_RX_FO); - device_printf(sc_if->msk_if_dev, "Rx FIFO overrun!\n"); - } /* GMAC Tx FIFO underrun. */ if ((status & GM_IS_TX_FF_UR) != 0) { CSR_WRITE_4(sc, MR_ADDR(sc_if->msk_port, TX_GMF_CTRL_T), |
