From owner-freebsd-stable@FreeBSD.ORG Mon Jun 10 00:59:37 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B711BBE2; Mon, 10 Jun 2013 00:59:37 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) by mx1.freebsd.org (Postfix) with ESMTP id 8BEBD11D3; Mon, 10 Jun 2013 00:59:37 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id y14so3924978pdi.16 for ; Sun, 09 Jun 2013 17:59:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=2bFSeVlEibFqNw2kNTYQJJwG0ft9pznexaJkVQJPMiE=; b=AreotbqTKsR9gZ9ALCEbE/0sfM96tcdjCJjAeophg66/YAx4fUl2cfn5pYhMqTLFUG BVDGxRLfdtKuOPOb92a6aHZt1AIih8ozyCoV4loZm7f6yTwXdYI+bGOKVTESLuKr+goB ET35T5PavEnl0t2q4Z0m/mgI6U1ZQL14oaUR3gpC+OBGmmmW9ChegbYQQRzWqUzbDhiX M8Crtsdz2dQEfYow9EymB0zp2b1XQD9I8c4JJWbh180A8evfWo6qdS6/FQiHSYsFlRMg yZsqFJkjYJ+9NHAHPoKzJBd7VxZFL1tMxHw4i6TJlb5339qkkqZf/yhCL8o5DKo3qiDv UDIQ== X-Received: by 10.68.251.133 with SMTP id zk5mr7818243pbc.75.1370825976978; Sun, 09 Jun 2013 17:59:36 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id ri8sm8269425pbc.3.2013.06.09.17.59.33 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 09 Jun 2013 17:59:35 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 10 Jun 2013 09:59:25 +0900 From: YongHyeon PYUN Date: Mon, 10 Jun 2013 09:59:25 +0900 To: Lev Serebryakov Subject: Re: fxp0 interface going up/down/up/down (dhclient related?) Message-ID: <20130610005925.GC3771@michelle.cdnetworks.com> References: <20130609104401.GA33827@icarus.home.lan> <1591834077.20130609211333@serebryakov.spb.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1591834077.20130609211333@serebryakov.spb.ru> User-Agent: Mutt/1.4.2.3i Cc: Jeremy Chadwick , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jun 2013 00:59:37 -0000 On Sun, Jun 09, 2013 at 09:13:33PM +0400, Lev Serebryakov wrote: > Hello, Jeremy. > You wrote 9 июня 2013 г., 14:44:01: > > JC> The issue is described in the 8.4-RELEASE Errata Notes; the driver is > JC> using the same driver version as in stable/9, hence you're experiencing > JC> the same problem. See Open Issues: > I had some memory, that I had had this problem on my router some time > (year? two years? three?) ago, and it was fixed somehow at then-HEAD > (9?) system with disabling link down event on fxp(4), caused by chip > reset after address setting. Is it deja-vu or true memory? There was a bug at the time but it was fixed long time ago. Current issue is different one but the end result looks very similar to the old bug.