Date: Tue, 16 Dec 2008 19:15:41 -0800 From: Bruce Cran <bruce@cran.org.uk> To: pyunyh@gmail.com Cc: current@freebsd.org Subject: Re: RTL8102E (if_re) doesn't work with -current Message-ID: <49486EDD.6060607@cran.org.uk> In-Reply-To: <20081217005106.GA66999@cdnetworks.co.kr> References: <4947E59A.8000408@cran.org.uk> <20081217005106.GA66999@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49486EDD.6060607>