From owner-freebsd-stable@FreeBSD.ORG Fri Aug 1 12:20:13 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 C78D51065702 for ; Fri, 1 Aug 2008 12:20:13 +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 827088FC18 for ; Fri, 1 Aug 2008 12:20:13 +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 B1AE3E9FD317 for ; Fri, 1 Aug 2008 14:20:11 +0200 (CEST) Received: from [217.236.6.45] (helo=zelda.local) by smtp08.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1KOtcB-0005gd-00 for freebsd-stable@freebsd.org; Fri, 01 Aug 2008 14:20:11 +0200 Date: Fri, 1 Aug 2008 14:20:05 +0200 From: Martin To: Message-ID: <20080801142005.473c17ca@zelda.local> 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_//ZCC3lHZ6IStEPMiFbQwJby"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX19PL8BctbCltHAelYqWIfvD2xyg95o6spDASPNO KKRkV8GdLmq0HI2KEQeFoQFdsPcPzOOsRnM1xaRuXHS6GkzEDL NNB0RwBTw= Subject: 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: Fri, 01 Aug 2008 12:20:13 -0000 --Sig_//ZCC3lHZ6IStEPMiFbQwJby Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello, I don't remember anymore when I reported it the first time. I think it was around 4.x or something like that. The em(4) bug is still there after years. Hasn't anyone really noticed yet that em(4) only appears when you boot FreeBSD with the interface physically attached to a switch for example? If you attach it later, after boot up, the interface won't power up and appear in the interface list (ifconfig)? Steps to reproduce: 1) Switch your PC/laptop off. Really OFF, no reboot. 2) Disconnect the em(4) NIC from your switch. 3) Boot FreeBSD. 4) Plug in the ethernet cable. 5) Tataa! All leds at the NIC stay off. You won't be able to use em(4) unless you reboot your machine. Something is not being initialized properly on em(4) devices, it seems.=20 I have had 3 of 3 em(4) NICs so far, where this bug shows up. And it's extremely annoying on Thinkpads, when you just want to plug in your laptop somewhere. -- Martin --Sig_//ZCC3lHZ6IStEPMiFbQwJby Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkiS/3UACgkQC3yNaKlBCg0rVACgokyotrDnFIIdoN2b/y56J4Qp is8An3GOJSF/It6om1AzDj5DHPX7bED7 =eQwX -----END PGP SIGNATURE----- --Sig_//ZCC3lHZ6IStEPMiFbQwJby--