From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 21:38:02 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 569C016A4DA for ; Fri, 7 Jul 2006 21:38:02 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E333543D45 for ; Fri, 7 Jul 2006 21:38:01 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0E45146BB4; Fri, 7 Jul 2006 17:38:01 -0400 (EDT) Date: Fri, 7 Jul 2006 22:38:01 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: User Freebsd In-Reply-To: <20060707181750.O1171@ganymede.hub.org> Message-ID: <20060707223609.N60542@fledge.watson.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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Pyun YongHyeon , Peter Jeremy , Atanas , freebsd-stable@FreeBSD.org, Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 21:38:02 -0000 On Fri, 7 Jul 2006, User Freebsd wrote: >> I think that I have patched, built and loaded the em(4) kernel module >> correctly. After applying the patch there were no rejects, before building >> the module I intentionally appended " (patched)" to its version string in >> if_em.c, and could see that in dmesg every time I loaded the module: em1: >> > > Is it possible that we're going at this issue backwards? It isn't the lack > of ARP packet going out that is causing the problems with moving IPs, but > that delay that we're seeing when aliasing a new IP on the stack? The ARP > packet *is* being attempted, but is timing out before the re-init is > completing? Yes -- basically, there are two problems: (1) A little problem, in which an arp announcement is sent before the link has settled after reset. (2) A big problem, in which the interface is gratuitously recent requiring long settling times. I'd really like to see a fix to the second of these problems (not resetting when an IP is added or removed, resulting in link renegotiation); the first one I'm less concerned about, although it would make some amount of sense to do an arp announcement when the link goes up. Robert N M Watson Computer Laboratory University of Cambridge