Wolfgang Walter wrote:
it seems that e1000 enables flow-control (rx pause frames) even if
the switch does not advertise flow control. This seems to get a
problem as (at least some) switches then forward pause frames
directed to the card from other hosts. We think there are hosts which
indeed
Wolfgang Walter wrote:
Hello,
it seems that e1000 enables flow-control (rx pause frames) even if the switch
does not advertise flow control. This seems to get a problem as (at least
some) switches then forward pause frames directed to the card from other
hosts. We think there are hosts
Brandeburg, Jesse wrote:
Wolfgang Walter wrote:
it seems that e1000 enables flow-control (rx pause frames) even if
the switch does not advertise flow control. This seems to get a
problem as (at least some) switches then forward pause frames
directed to the card from other hosts. We think
Hello,
it seems that e1000 enables flow-control (rx pause frames) even if the switch
does not advertise flow control. This seems to get a problem as (at least
some) switches then forward pause frames directed to the card from other
hosts. We think there are hosts which indeed do this in the
On Tue, 19 Jul 2005, Jason L Tibbitts III wrote:
mii-tool -v eth0:
eth0: negotiated 100baseTx-FD flow-control, link ok
product info: vendor 00:50:43, model 2 rev 3
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD
On 7/19/05, Jason L Tibbitts III [EMAIL PROTECTED] wrote:
I'm having trouble enabling flow control with the e1000 driver. I'm
running Fedora Core 3 (currently a 2.6.11-ish kernel until the new one
doesn't kill SMP machines). The e1000 driver is version
5.6.10.1-k2-NAPI. The Ethernet ports
JB == Jesse Brandeburg [EMAIL PROTECTED] writes:
JB Flow control should be supported, but it is autonegotiated at link
JB time. How do you know it isn't on?
Thanks for the response. I'm going on two pieces of information:
1) The switch indicates that flow control is not on
2) UDP NFS is
