Date: Wed, 28 Jun 2006 02:02:28 +0000 (GMT) From: wpaul@FreeBSD.ORG (Bill Paul) To: keramida@freebsd.org (Giorgos Keramidas) Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/share/man/man4 re.4 src/sys/dev/re if_re.c src/sys/dev/mii rgephy.c src/sys/pci if_rlreg.h Message-ID: <20060628020228.EFC6716A403@hub.freebsd.org> In-Reply-To: <20060627172841.GA1310@gothmog.pc> from Giorgos Keramidas at "Jun 27, 2006 08:28:41 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> On 2006-06-26 20:31, Bill Paul <wpaul@freebsd.org> wrote:
> > wpaul 2006-06-26 20:31:32 UTC
> >
> > FreeBSD src repository
> >
> > Modified files:
> > share/man/man4 re.4
> > sys/dev/re if_re.c
> > sys/dev/mii rgephy.c
> > sys/pci if_rlreg.h
> > Log:
> > Add support for the RealTek 8169SC/8110SC and RTL8101E devices. The
> > latter is a PCIe 10/100 chip.
> >
> > Finally fix the EEPROM reading code so that we can access the EEPROMs on all
> > devices. In order to access the EEPROM, we must select 'EEPROM programming'
> > mode, and then set the EEPROM chip select bit. Previously, we were setting
> > both bits simultaneously, which doesn't work: they must be set in the
> > right sequence.
> > [...]
>
> Something in this commit breaks re(4) interface here.
>
> With a kernel after this change, no re(4) interfaces appear to attach:
[...]
Somewhere in the above space, there should have been a COMPLETE dmesg
output from your system, but apparently the e-mail gremlins ate it.
Given that I actually tested an RTL8111B/RTL8168B sample card and it
worked fine with this code, RIGHT BEFORE I CHECKED IT IN, I'm forced
to conclude that this problem is one of your own devising. I'm sure
there's a big fat clue to the problem in the dmesg output that you
didn't send.
> # pficonf -lv
> [...]
> none2@pci2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00
> vendor = 'Realtek Semiconductor'
> class = network
> subclass = ethernet
>
> Reverting this change fixes my re0 interface, but I am not sure I can
> track down why it broke. Any ideas about where to look for the reason
> my re(4) NIC fails to attach after this change?
You didn't give me enough information to answer this question. Since
you declined to state EXACTLY what you did, I can't tell you where
you went wrong.
-Bill
--
=============================================================================
-Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu
wpaul@windriver.com | Wind River Systems
=============================================================================
<adamw> you're just BEGGING to face the moose
=============================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060628020228.EFC6716A403>