From owner-freebsd-stable@FreeBSD.ORG Sat Aug 2 20:40:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC9411065670 for ; Sat, 2 Aug 2008 20:40:50 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.freebsd.org (Postfix) with ESMTP id 8467E8FC17 for ; Sat, 2 Aug 2008 20:40:50 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp08.web.de (fmsmtp08.dlan.cinetic.de [172.20.5.216]) by fmmailgate01.web.de (Postfix) with ESMTP id BCC0CEA162AB; Sat, 2 Aug 2008 22:40:48 +0200 (CEST) Received: from [217.236.1.240] (helo=localhost) by smtp08.web.de with asmtp (WEB.DE 4.109 #226) id 1KPNuC-0007Oa-00; Sat, 02 Aug 2008 22:40:48 +0200 Date: Sat, 2 Aug 2008 22:40:46 +0200 From: Martin To: Torfinn Ingolfsen Message-ID: <20080802224046.3b547283@web.de> In-Reply-To: <20080802125553.d9c83a55.torfinn.ingolfsen@broadpark.no> References: <20080801142005.473c17ca@zelda.local> <20080801124224.GA17183@eos.sc1.parodius.com> <20080802070015.7f64c862@web.de> <20080802125553.d9c83a55.torfinn.ingolfsen@broadpark.no> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX18O38PoU+3jVU2VBBFeJ6y+OCyaFdm5q0nREOYZ ENuITbODP9GkEjOqOI4CmpHSPMTC14bMkz3VOplGFVq0JfcPCI 1XJAR/gJM= Cc: freebsd-stable@freebsd.org Subject: Re: em(4) on FreeBSD is sometimes annoying 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: Sat, 02 Aug 2008 20:40:50 -0000 On Sat, 02 Aug 2008 12:55:53 +0200 Torfinn Ingolfsen wrote: > Just to be sure: also if the first command you try on the interface is > 'ifconfig up'? Hello Torfinn, good point, no. The problem appears when the first thing called on this interface is dhclient (caused by ifconfig_em0="DHCP"). I could also provoke this behavior after the interface was once up had an IP and was working (ping). All I need to do is to disconnect the NIC from the switch when I type "/etc/rc.d/netif restart". I have noticed further strange effects here. The behavior seems to be even more complex. After I typed "/etc/rc.d/netif restart", I waited until I get "giving up" message. Then I plugged the cable in. After about 30 seconds the link LED was on. I noticed that at this point I couldn't get an address using DHCP. So I disconnected physically the NIC (no cable) and link LED was still on! ifconfig showed me "state: active" with no cable plugged in. After further 30 seconds the LED went off. I attached the NIC again to the switch again and after 30 seconds again I got some other effect. The link LED went on (status: active) and the data LED was permanently blinking (about 2,5 times a second). I pulled the cable again and now the link LED is still on and the data LED still blinking (since about 10 minutes already). By the way... Now I'm typing this E-Mail without an ethernet cable plugged in and the link status LED is still on and the other data LED is blinking. -- Martin