From owner-freebsd-stable@FreeBSD.ORG Sat Aug 2 04:47:31 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 034761065671 for ; Sat, 2 Aug 2008 04:47:31 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate02.web.de (fmmailgate02.web.de [217.72.192.227]) by mx1.freebsd.org (Postfix) with ESMTP id 75A898FC0C for ; Sat, 2 Aug 2008 04:47:30 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp06.web.de (fmsmtp06.dlan.cinetic.de [172.20.5.172]) by fmmailgate02.web.de (Postfix) with ESMTP id CA711E7D40DB; Sat, 2 Aug 2008 06:47:28 +0200 (CEST) Received: from [217.236.1.240] (helo=localhost) by smtp06.web.de with asmtp (WEB.DE 4.109 #226) id 1KP91c-0007mT-00; Sat, 02 Aug 2008 06:47:28 +0200 Date: Sat, 2 Aug 2008 06:47:27 +0200 From: Martin To: "Jack Vogel" Message-ID: <20080802064727.042d5e3d@web.de> In-Reply-To: <2a41acea0808010924u22603c61p10e47237fad5b6fb@mail.gmail.com> References: <20080801142005.473c17ca@zelda.local> <20080801154208.W6085@fledge.watson.org> <2a41acea0808010924u22603c61p10e47237fad5b6fb@mail.gmail.com> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX1+5oilQu9+oQ650lJlVGcywe+SyV9Q9CR9skMeW Xv/b+FW51vVPG6sGy9NZowP/bN6sCVaMWSrF52CTNe0FHfSagN uPJzmiYFo= Cc: jfv@freebsd.org, freebsd-stable@freebsd.org, Robert Watson 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 04:47:31 -0000 On Fri, 1 Aug 2008 09:24:53 -0700 "Jack Vogel" wrote: > If the poster gives me EXACT hardware list I will see about repro'ing the > problem inhouse. We do not do much of anything with laptops but I > will see. Oh and a pciconf would help too. Hi Jack, pciconf -lv gives me: em0@pci0:2:0:0: class=0x020000 card=0x200117aa chip=0x109a8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82573L Intel PRO/1000 PL Network Adaptor' class = network subclass = ethernet One thing, I have to add. I described the behavior wrong. The adapter actually IS available in the interface list, but it gets "no carrier". Sorry for that. This is what I get from ifconfig when the NIC is plugged in: em0: flags=8843 metric 0 mtu 1500 options=19b ether xx:xx:xx:xx:xx:xx media: Ethernet autoselect status: no carrier All LEDs are off. Device was found on boot: em0: port 0x3000-0x301f mem 0xee000 000-0xee01ffff irq 16 at device 0.0 on pci2 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: xx:xx:xx:xx:xx:xx -- Martin