From owner-freebsd-stable@FreeBSD.ORG Mon Aug 4 08:53:45 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 BC1401065670 for ; Mon, 4 Aug 2008 08:53:45 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate03.web.de (fmmailgate03.web.de [217.72.192.234]) by mx1.freebsd.org (Postfix) with ESMTP id 46F9C8FC0A for ; Mon, 4 Aug 2008 08:53:45 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp06.web.de (fmsmtp06.dlan.cinetic.de [172.20.5.172]) by fmmailgate03.web.de (Postfix) with ESMTP id 765EAE5DFFCB; Mon, 4 Aug 2008 10:53:43 +0200 (CEST) Received: from [217.236.48.156] (helo=zelda.local) by smtp06.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1KPvp1-0001s8-00; Mon, 04 Aug 2008 10:53:43 +0200 Date: Mon, 4 Aug 2008 10:53:35 +0200 From: Martin To: "Jack Vogel" Message-ID: <20080804105335.4cd5df47@zelda.local> In-Reply-To: <2a41acea0808021601u13147294r9dc44a737119648@mail.gmail.com> 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> <2a41acea0808021601u13147294r9dc44a737119648@mail.gmail.com> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/VYtn9nwgbhwGaqfJ+p++luG"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX1/l8feK13XOHUGKa22mGtIg4sB2ak7NSWZkFl1I CcA+KTDDPSdUfkkQ560zKJFZCL63kYxA0Kgqe4ZQjMEr4cgc6q rG+75GSUI= 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: Mon, 04 Aug 2008 08:53:45 -0000 --Sig_/VYtn9nwgbhwGaqfJ+p++luG Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sat, 2 Aug 2008 16:01:35 -0700 schrieb "Jack Vogel" : Hi, > > 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. >=20 > Well DUH, the agent exited, thats why it said "giving up" :) > That ain't complex behavior, its behaving as designed. I'm describing the circumstances WHEN everything happens. I was trying to show you that even the cable is plugged in you cannot get an IP. The NIC is in a kind of "dead" state. > 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. I have this problem with every kind of switch. The switch at home is a 100Mbit switch made by Digitus (5-port). > 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? This is true except for the "forcing the speed" part. It's set to "media: Ethernet autoselect". > I asked for a hardware list, now that includes the switch. Digitus DN-5001C: http://www.amazon.de/Assmann-Digitus-DN-5001C-Switch-Fast/dp/B0009FHTWI -- Martin --Sig_/VYtn9nwgbhwGaqfJ+p++luG Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkiWw48ACgkQC3yNaKlBCg38mwCcDKdfQcFlfV1+oDtju5HN4Diu a8EAoJFg62rMZKPmBgg5DVADDyK5+vdQ =Jw9l -----END PGP SIGNATURE----- --Sig_/VYtn9nwgbhwGaqfJ+p++luG--