From owner-freebsd-current@FreeBSD.ORG Wed Dec 17 03:15:56 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 215B71065686 for ; Wed, 17 Dec 2008 03:15:56 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [66.246.138.153]) by mx1.freebsd.org (Postfix) with ESMTP id EBEB78FC1B for ; Wed, 17 Dec 2008 03:15:55 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id A40771901C; Tue, 16 Dec 2008 22:15:54 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on muon X-Spam-Level: X-Spam-Status: No, score=-2.2 required=8.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 Received: from [66.45.160.84] (unknown [66.45.160.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Tue, 16 Dec 2008 22:15:54 -0500 (EST) Message-ID: <49486EDD.6060607@cran.org.uk> Date: Tue, 16 Dec 2008 19:15:41 -0800 From: Bruce Cran User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: pyunyh@gmail.com References: <4947E59A.8000408@cran.org.uk> <20081217005106.GA66999@cdnetworks.co.kr> In-Reply-To: <20081217005106.GA66999@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: RTL8102E (if_re) doesn't work with -current 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: Wed, 17 Dec 2008 03:15:56 -0000 Pyun YongHyeon wrote: > On Tue, Dec 16, 2008 at 09:30:02AM -0800, Bruce Cran wrote: > > I just upgraded an HP Pavillion laptop from 7.1-RC1 to 8-CURRENT last > > night and now the network doesn't work. This laptop has a RTL8102E > > chip, and no errors appear in the logs - it attaches and doesn't claim > > to have any TX/RX errors, but it just doesn't do anything. I've > > attached the dmesg from a verbose boot. I've seen messages saying > > there might be issues with MSI interrupts - is that possibly an issue here? > > > > No, it is in disabled state by default. > The issue could be related with link state tracking code in re(4). > Would you show me the output of "devinfo -rv | grep rlphy"? > How about unplugging/replugging UTP cable? > Does it make any difference? > devinfo provides the output: rlphy0 pnpinfo oui=0x20 model=0x20 rev=0x1 at phyno=1 I let the startup continue so that dhclient was still running in the background, and I started getting lots of messages: arp: 00:1e:ec:72:2b:8e attempts to modify permanent entry for 0.0.0.0 on re0 After unplugging the replugging the UTP cable the messages re0: link state changed to DOWN re0: link state changed to UP apppeared in the logs but dhclient still didn't get any replies, and the arp messages started again. -- Bruce Cran