From owner-freebsd-stable@FreeBSD.ORG Mon Aug 4 10:00:17 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 1C5771065672 for ; Mon, 4 Aug 2008 10:00:17 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id D062F8FC0A for ; Mon, 4 Aug 2008 10:00:16 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by yw-out-2324.google.com with SMTP id 9so928165ywe.13 for ; Mon, 04 Aug 2008 03:00:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:mime-version:content-type:content-transfer-encoding :content-disposition; bh=6O5T4eEO4ck/ur5PEywVDIoxE6UIo8EuILv+b3/MTTU=; b=BAzPLsujMHKB27IZ0qCiVv0ig6oFEG38lrVQcDof3zOHHCrbaCjsPrSrAmDfwTY7t8 pydoePBLv/ubtV216iN5JTDGe3SZ3nfFLhDleH7fjy5e442y+vg0EMYzWwTsmUlhMMuk ZZuUQhMMF7X7N7L2WYTi1bBCiBotaX+9OxoSM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:mime-version :content-type:content-transfer-encoding:content-disposition; b=pBM1lduXuhEELuXjXfVBf7xxCYRZphiAeij3NkEpDJjCdt1GPnp5RYXeuC23r0Dwlx zai58lCHZxtooWG9RVu4j80g7YQ9RReMXjNJOKOEmrs2+n3dn1NQ+p8kIYRqPv0Pf1go zLarm3m1bKumzu0fYA5FW/A9TvLQYT/z9zgK4= Received: by 10.150.216.3 with SMTP id o3mr988023ybg.221.1217844016178; Mon, 04 Aug 2008 03:00:16 -0700 (PDT) Received: by 10.150.229.11 with HTTP; Mon, 4 Aug 2008 03:00:16 -0700 (PDT) Message-ID: Date: Mon, 4 Aug 2008 11:00:16 +0100 From: "Chris Rees" To: Martin , "Torfinn Ingolfsen" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 Reply-To: utisoft@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, 04 Aug 2008 10:00:17 -0000 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. > > 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 > I may have misunderstood the purpose of this, but do you have the bpf compiled into your kernel? If you're having DHCP troubles, this could be a problem. Chris