From owner-freebsd-stable@FreeBSD.ORG Sat Aug 2 05:00:20 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 B257C1065684 for ; Sat, 2 Aug 2008 05:00:20 +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 6F25C8FC13 for ; Sat, 2 Aug 2008 05:00:20 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp05.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) by fmmailgate01.web.de (Postfix) with ESMTP id C8027EA0B3DB; Sat, 2 Aug 2008 07:00:18 +0200 (CEST) Received: from [217.236.1.240] (helo=localhost) by smtp05.web.de with asmtp (WEB.DE 4.109 #226) id 1KP9E2-0002Oi-00; Sat, 02 Aug 2008 07:00:18 +0200 Date: Sat, 2 Aug 2008 07:00:15 +0200 From: Martin To: Jeremy Chadwick Message-ID: <20080802070015.7f64c862@web.de> In-Reply-To: <20080801124224.GA17183@eos.sc1.parodius.com> References: <20080801142005.473c17ca@zelda.local> <20080801124224.GA17183@eos.sc1.parodius.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+0iiGs6Q1kppAgSxbWtisZe9tmaE2J3DOUUEGk 7A7H7JqEuG/cAwBnB2T+FbgNPScg3cCslMkOT99ZwVa4jXbMoP rLhB66mzI= 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 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 05:00:20 -0000 On Fri, 1 Aug 2008 05:42:24 -0700 Jeremy Chadwick wrote: Hi Jeremy, > Most commonly what you're reporting is the result of a switch upstream > which isn't fully compatible or properly doing 802.3u auto-neg. It is attached to a cheap switch here. Also at my office it is not coming up. And I have NEVER this problem when the laptop is already plugged in. > Rebooting the machine (thus tearing down link hard, and resetting the > entire chip) often works in this situation. You can also try setting > the speed and duplex (media and mediaopt) in your ifconfig_emX line in > rc.conf to see if that helps (on some switches it does). This is what I get, when I plug it in and try to configure something: # ifconfig em0 mediaopt full-duplex ifconfig: SIOCSIFMEDIA (media): Device not configured But it accepts up, down and even inet
. LEDs are off and still "no carrier". > The behaviour you're reporting I've seen on old 3Com XL 509x cards with > Cisco switches, for example. I've heard of the autonegotiation problem, but it rather looks to my as if something is getting initialized during BIOS boot and FreeBSD is not doing it correctly. > I have a Thinkpad T60p. I'll try booting FreeBSD on it next week and > see if I can reproduce the behaviour. I'll also include what switch > brands/models are being plugged into. Once again. I made a mistake describing the problem. I'm really sorry for this. The interface actually appears in the ifconfig list, but I cannot get it up. It always shows "no carrier". No matter what I try. -- Martin