Date: Thu, 06 Jul 2006 19:11:57 -0700 From: Atanas <atanas@asd.aplus.net> To: pyunyh@gmail.com Cc: Peter Jeremy <peterjeremy@optushome.com.au>, freebsd-stable@freebsd.org, Michael Vince <mv@thebeastie.org>, User Freebsd <freebsd@hub.org> Subject: Re: em device hangs on ifconfig alias ... Message-ID: <44ADC2ED.4070904@asd.aplus.net> In-Reply-To: <20060707010341.GD82406@cdnetworks.co.kr> References: <44A3817F.4030105@thebeastie.org> <20060629092154.GE742@turion.vk2pj.dyndns.org> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
Pyun YongHyeon said the following on 7/6/06 6:03 PM: > > Hmm, that's strange. I've double checked that stock em(4) didn't > generate ARP packets when its addresses were changed. So I made > em(4) generate ARP. Could you see a gratuitous ARP with tcpdump > when you change its address? > I just left a "tcpdump -n arp host 10.10.64.40" on a third machine sniffing around and tested all em module versions I had (the stock 6.1, 6-STABLE and 6-STABLE with your patch), but got silence on all three: EM# ifconfig em1 inet alias 10.10.64.40 <nothing> EM# ifconfig em1 inet -alias 10.10.64.40 <nothing> The fxp driver appears to send something on startup and nothing on shutdown: FXP# ifconfig fxp0 inet alias 10.10.64.40 18:41:54.584059 arp who-has 10.10.64.40 tell 10.10.64.40 FXP# ifconfig fxp0 inet -alias 10.10.64.40 <nothing> When I manually arping the em alias after startup (i.e. simulate what fxp does), everything works as expected: EM# ifconfig em1 inet alias 10.10.64.40 <nothing> EM# arping -c1 -S10.10.64.40 10.10.64.40 18:46:07.808701 arp who-has 10.10.64.40 tell 10.10.64.40 EM# ifconfig em1 inet -alias 10.10.64.40 <nothing> It appears that this is what the em driver is supposed to do, or at least fxp does it in this way. > This is other issue. em(4) performs two time-consuming operations > in its initialization routine. One is DMA tag/map creation and the > other is checksumming EEPROM contents in init routine. > I have an experimental patch for it but let's fix one at a time. > OK, let's put that aside for now. Regards, Atanas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44ADC2ED.4070904>