From owner-freebsd-stable@FreeBSD.ORG Tue Aug 5 10:57: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 371B51065675 for ; Tue, 5 Aug 2008 10:57: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 B1FDC8FC14 for ; Tue, 5 Aug 2008 10:57:49 +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 E5F67EA3A278; Tue, 5 Aug 2008 12:57:47 +0200 (CEST) Received: from [217.236.9.39] (helo=zelda.local) by smtp08.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1KQKEd-0003x5-00; Tue, 05 Aug 2008 12:57:47 +0200 Date: Tue, 5 Aug 2008 12:57:35 +0200 From: Martin To: "Jack Vogel" Message-ID: <20080805125735.5673ce35@zelda.local> In-Reply-To: <2a41acea0808041212g4d8790dds712e9e2309827f75@mail.gmail.com> References: <20080801142005.473c17ca@zelda.local> <20080802064727.042d5e3d@web.de> <2a41acea0808021034g588fdc77w50797f473e8809b0@mail.gmail.com> <20080804113448.0a4b3991@zelda.local> <20080804102307.GA28928@eos.sc1.parodius.com> <20080804125138.59ed0252@zelda.local> <20080804174458.4dda8369@zelda.local> <2a41acea0808041018nc60b3uf53d2e898a73d9a9@mail.gmail.com> <48973DD9.20303@alaska.net> <20080804205252.74141013@web.de> <2a41acea0808041212g4d8790dds712e9e2309827f75@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_/gKnzqrKyofwDI4w7EE92pDw"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX18ZcCLaDVAloz//rfyY4P3DAKjkeniGVsjXx+Sx vT5HJZukDC0T8ZlnBx7Xr1uC9ctAWbimjMmJgFnEdZVRhNUT9P 4LCk1DtYk= Cc: freebsd-stable@freebsd.org, Royce Williams 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: Tue, 05 Aug 2008 10:57:50 -0000 --Sig_/gKnzqrKyofwDI4w7EE92pDw Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Mon, 4 Aug 2008 12:12:24 -0700 schrieb "Jack Vogel" : > OK, so your EEPROM is does not have the bug. As I was > saying before, I would like to see what back to back behavior is. >=20 > And, BTW, back to back does NOT mean hook to the switch, > that's the very thing that is suspicious. It means NIC to NIC, > no DHCP, assigned addresses. And then see that you pass > traffic, and then unhook cable, see if link goes down, reconnect > and it should go up. With no /etc/rc.d/netif script involved during startup everything always works as expected. If I comment the line ifconfig_re0=3D"DHCP" and start my laptop. I can assign the address. I can ping the other NIC. If can unhook the cable the LED goes off, link goes down, I can plug it in again, I can ping again. I have also no problems if I start without ifconfig_re0=3D"DHCP" and run "dhclient em0" while ethernet cable is unplugged. If I plug it in again, everything works like above. But: If I startup with ifconfig_em0=3D"DHCP" AND (binary and!) no cable nothing of this works correctly. There must be something ifconfig_em=3D"DHCP" causes on startup that running dhclient does not cause and that provokes the dead state. > Oh, and exactly what kernel, and driver revision are you using. Kernel is FreeBSD-STABLE compile date Mon Aug 4 13:41:43 CEST 2008. It's GENERIC. The em(4) driver is the one used in this STABLE version of yesterday. I should perhaps mention that I have some other problems with this laptop. I cannot boot with a PCMCIA wireless card (atheros) already in the slot, or I get 100% load on cbb(4) and the system is not usable. If I boot without the Atheros card and I plug it in later, it mostly is detected. AND I get sometimes an NMI when Atheros card is in use AND (binary and again!) the laptop is on battery. This happens also on Linux. AND the laptop will almost never recognize the Atheros card, if I am using a text terminal with high resolution (set by vidcontrol MODE_280 with VESA support compiled in; cannot reproduce now, because I'm using GENERIC). I don't know if these things are related. I will get some other laptop in one or two months. I hope these things won't bother me anymore. -- Martin --Sig_/gKnzqrKyofwDI4w7EE92pDw Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkiYMh8ACgkQC3yNaKlBCg14ZQCeKv77zwS7uq5cIvbbzfSNxlhQ reMAniFqnX/mgFelj5WnWzkImrs1YeF7 =mr+i -----END PGP SIGNATURE----- --Sig_/gKnzqrKyofwDI4w7EE92pDw--