Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 8 Jul 2006 12:05:58 -0300 (ADT)
From:      User Freebsd <freebsd@hub.org>
To:        Michael Vince <mv@thebeastie.org>
Cc:        Pyun YongHyeon <pyunyh@gmail.com>, Peter Jeremy <peterjeremy@optushome.com.au>, Atanas <atanas@asd.aplus.net>, Robert Watson <rwatson@FreeBSD.org>, freebsd-stable@FreeBSD.org
Subject:   Re: em device hangs on ifconfig alias ...
Message-ID:  <20060708120252.K1799@ganymede.hub.org>
In-Reply-To: <44AF5EB2.2040701@thebeastie.org>
References:  <20060629083130.X1229@ganymede.hub.org> <44A4A02A.9060802@thebeastie.org> <20060630012615.Q1103@ganymede.hub.org> <44A57B71.6020201@asd.aplus.net> <20060701035416.GC54876@cdnetworks.co.kr> <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <44AF5EB2.2040701@thebeastie.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 8 Jul 2006, Michael Vince wrote:

> I thought I remember a developer working on the em driver saying just 
> before 6.1 was released that this reset was needed and couldn't be 
> avoided to ensure performance of the device to work at its best, I can't 
> remember his explanation, but this topic has come up before, of course 
> anything is possible to fix.

The thing is, and I may be mis-understanding the explanations so far, the 
'reset' is to renegotiate the connection ... if that is the case, and both 
the switch and the interface are already locked at a speed (in my case, 
both are hard coded to "100baseTX full duplex", then what is there to 
re-negotiate?

And, why does it appear that *only* the em driver/interface requires this? 
I run bge and fxp interfaces on this same network, against the same 
switch, all locked at the same speed, and only the em driver exhibits this 
problem ... in fact, its only the *newer* em driver that does, as I have 
one server on the network, using an em interface, that is running an older 
FreeBSD 4.x kernel, that performs the same as the bge/fxp (ie. perfectly)

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org                              MSN . scrappy@hub.org
Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060708120252.K1799>