From owner-freebsd-stable@FreeBSD.ORG Sat Aug 2 23:01:37 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 CE013106566B for ; Sat, 2 Aug 2008 23:01:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by mx1.freebsd.org (Postfix) with ESMTP id 54C688FC0C for ; Sat, 2 Aug 2008 23:01:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so2142617fkk.11 for ; Sat, 02 Aug 2008 16:01:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=nKa/SM37/X5qPi4HQ4Oxsf9DzYzE8W5k0p09NiWZfNk=; b=ZEjzTvA0qBqMU63aF4jiBuIkhN7GNkfeptfFiVOJDAA5bcJvZs9rx/elG3kqBXpS5O h1CbVBYNNUI5/RhKj2WfMDxuX173lD5FZCyR6PRfG0I7OJwxIOld6QDkOwm5IP3T3u0y iIY8vPqSqiWni8TA9Vo8gKvGyYmaRMx0kHv0E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=lq9PpOnvc6sMPFK1u3ClmQLhIITIvhmbpX8wvcfilg0J23Qror0ilH+IM7TXTlsai1 7qtQGsJQaDHdfFZkS7BQFfR5NlLYhKZmhn9ngujeQbbeuZvGjK9lLfh/qO5+kHbtFTtr kVEz3PsYlvjhakR/p3WHb4tmo4F9WvuFmJ6uM= Received: by 10.125.89.10 with SMTP id r10mr630004mkl.77.1217718095884; Sat, 02 Aug 2008 16:01:35 -0700 (PDT) Received: by 10.125.74.17 with HTTP; Sat, 2 Aug 2008 16:01:35 -0700 (PDT) Message-ID: <2a41acea0808021601u13147294r9dc44a737119648@mail.gmail.com> Date: Sat, 2 Aug 2008 16:01:35 -0700 From: "Jack Vogel" To: Martin In-Reply-To: <20080802224046.3b547283@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080801142005.473c17ca@zelda.local> <20080801124224.GA17183@eos.sc1.parodius.com> <20080802070015.7f64c862@web.de> <20080802125553.d9c83a55.torfinn.ingolfsen@broadpark.no> <20080802224046.3b547283@web.de> Cc: Torfinn Ingolfsen , 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 23:01:38 -0000 On Sat, Aug 2, 2008 at 1:40 PM, Martin wrote: > 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. Well DUH, the agent exited, thats why it said "giving up" :) That ain't complex behavior, its behaving as designed. > 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). Ya, so the update is slow, the fact that the LED is blinking means you have an autoneg failure, so again, its your switch not the NIC. Let me guess, you have some 100Mb home router and you are trying to plug a gig nic into it and forcing the speed maybe? I asked for a hardware list, now that includes the switch. Jack