From owner-freebsd-current@FreeBSD.ORG Tue Jul 21 02:57:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E025106564A for ; Tue, 21 Jul 2009 02:57:39 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-qy0-f204.google.com (mail-qy0-f204.google.com [209.85.221.204]) by mx1.freebsd.org (Postfix) with ESMTP id 483428FC12 for ; Tue, 21 Jul 2009 02:57:38 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by qyk42 with SMTP id 42so2204464qyk.3 for ; Mon, 20 Jul 2009 19:57:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/y8FKf8TJ4QaeYkGUmNRf3uErbyLx9bHNOLheLOClCo=; b=eybf4URhNqcRip6KZNOe2d51oe2cOmRfTM9y6G4oFVCteEu8L8SQVPqRU9qTlDn8ay pXn93UVZNgeOo5eHQlfkcfnZkPmq5uX5e+jMS5RuPipYhuU2/3Q2HjNQFML8ZsF/UsqB zVrpecrcjV6fClgjamg+2Xfjr4YEgkX+c0KNM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=l6r6GKZTBcrWbkQMj9j0+PpJai019LRF0nTEV/z3yFENV6KJa9dBzlaOCd54k1QvgY JgRdbOpJEXCmGYy8KQApDymwur5lfia6fDjsfNvVo8nwPE7LTQrRFkWutm4aCeCck8gU Mlmzrb3x1xPxusH6+wNhwmAZCgP20Ds/ECiJQ= MIME-Version: 1.0 Received: by 10.229.80.78 with SMTP id s14mr885487qck.101.1248145058442; Mon, 20 Jul 2009 19:57:38 -0700 (PDT) In-Reply-To: <4A651E50.6000508@doghouserepair.com> References: <4A651E50.6000508@doghouserepair.com> Date: Mon, 20 Jul 2009 21:57:38 -0500 Message-ID: <11167f520907201957h380601a7m18109be634da45c7@mail.gmail.com> From: "Sam Fourman Jr." To: Ryan Rogers Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: nfe problem on 8.0-BETA2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2009 02:57:39 -0000 On Mon, Jul 20, 2009 at 8:48 PM, Ryan Rogers wrote: > I'm running 8.0-BETA2/amd64 on a system that has on-board ethernet. =A0It= is > detected by FreeBSD as the following: > > nfe0: port 0xac00-0xac07 mem > 0xcfffa000-0xcfffafff,0xcfff9000-0xcfff90ff,0xcfff8000-0xcfff800f irq 22 = at > device 17.0 on pci0 > miibus1: on nfe0 > e1000phy0: PHY 1 on miibus1 > e1000phy0: =A010baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > > The problem is, I can't get packets to move across the interface. =A0I kn= ow > that the interface works in Windows as well as Ubuntu, but it looks like > it's failing to get fully configured in FreeBSD. =A0The output of ifconfi= g > nfe0 is: > > nfe0: flags=3D8843 metric 0 mtu 1= 500 > =A0 =A0 =A0 =A0options=3D19b > =A0 =A0 =A0 =A0ether 00:04:4b:01:8c:0b > =A0 =A0 =A0 =A0inet 10.10.10.3 netmask 0xffffff00 broadcast 10.10.10.255 > =A0 =A0 =A0 =A0media: Ethernet autoselect (none) > =A0 =A0 =A0 =A0status: active > > The part that I find odd is "media: Ethernet autoselect (none)". =A0If I > manually force it to "media 1000baseT mediaopt full-duplex", that line > becomes "media: 1000baseT full-duplex (10baseT/UTP half-duplex)". Still, = the > interface is dead. > > I found PR kern/127910 which describes the same problem, except for > 7.0-RELEASE. =A0There's been no activity on that for 9 months though (asi= de > from my update today). =A0Can anyone offer me any insight on this? > > Thanks, > Ryan I can confirm this is a nfe problem, I first reported it to the mailing list a few weeks back under the subject FreeBSD 8 BETA1 DHCP trouble. http://groups.google.co.jp/group/muc.lists.freebsd.current/browse_thread/th= read/ba7b35e561d3e868 I have several different motherboards with nfe nics, My findings are as fol= lows. on a FreeBSD -CURRENT snapshot dated 6-1-2009 dhcp works as expected. somewhere after ~ 6-6-2009 something broke. dhclient nfe0 DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 9 No DHCPOFFERS received. No working leases in persistent database - sleeping. the odd thing is that on motherboards that have dual nfe nics nfe1 always works,and nfe0 is always broke. on motherboards that have only a single nfe interface nfe0 is indeed broke. on a dual nic motherboard, if you go into BIOS and disable one of the LAN devices. DHCP will fail if the interface name is nfe0 even though it worked 5 min before when that same nic and MAC address had the nfe1 name. This entire thing is odd :) Sam Fourman Jr.