Date: Mon, 20 Oct 2008 16:11:55 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Norikatsu Shigemura <nork@FreeBSD.org> Cc: Daniel Gerzo <danger@FreeBSD.org>, stable@FreeBSD.org, yongari@FreeBSD.org Subject: Re: re0 problem Message-ID: <20081020071155.GH38923@cdnetworks.co.kr> In-Reply-To: <20081020012504.95adc0ca.nork@FreeBSD.org> References: <755632516.20081018001504@rulez.sk> <20081018020248.GB31303@cdnetworks.co.kr> <20081020012504.95adc0ca.nork@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 20, 2008 at 01:25:04AM +0900, Norikatsu Shigemura wrote: > Hi Pyun! > > On Sat, 18 Oct 2008 11:02:48 +0900 > Pyun YongHyeon <pyunyh@gmail.com> wrote: > > re(4) didn't require special PHY handling for 8169/8110 > > controllers. Did it ever work on older FreeBSD releases? I vaguely > > remember nork@ (Norikatsu Shigemura) also said Carbus GbE > > (RTL8169SBL) is not working but he could see successful attachment > > of rgephy(4). > > How about plugging UTP cable to controller before loading driver? > > On the latest 8-current, I got a probe failed: > > FreeBSD pelsia.ninth-nine.com 8.0-CURRENT FreeBSD 8.0-CURRENT #28: Sun Oct 12 21:55:35 JST 2008 nork@pelsia.ninth-nine.com:/usr/obj/usr/src/sys/PELSIA amd64 > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > pcib3: <ACPI PCI-PCI bridge> at device 0.0 on pci2 > pci3: <ACPI PCI bus> on pcib3 > re0: <RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet> port 0xa000-0xa0ff mem 0xf0300000-0xf03001ff irq 16 at device 0.0 on pci3 > re0: Chip rev. 0x10000000 > re0: MAC rev. 0x00000000 > re0: PHY write failed > re0: PHY write failed > re0: PHY read failed > re0: MII without any phy! > device_attach: re0 attach returned 6 > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > But, old current is ok. > > FreeBSD melfina.ninth-nine.com 8.0-CURRENT FreeBSD 8.0-CURRENT #74: Thu Aug 28 05:24:38 JST 2008 nork@melfina.ninth-nine.com:/usr/obj/usr/src/sys/MELFINA i386 > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > re0: <RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet> port 0x3100-0x31ff mem 0xb0103000-0xb01031ff irq 22 at device 0.0 on cardbus0 > re0: Reserved 0x200 bytes for rid 0x14 type 3 at 0xb0103000 > cbb0: Opening memory: > cbb0: Normal: 0xb0103000-0xb0103fff > re0: Chip rev. 0x10000000 > re0: MAC rev. 0x00000000 > miibus1: <MII bus> on re0 > rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus1 > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > re0: bpf attached > re0: Ethernet address: 00:e0:4c:77:ab:e8 > re0: [MPSAFE] > re0: [FILTER] > rgephy0: detached > miibus1: detached > cbb0: Opening memory: > re0: detached > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Hmm, that's odd. I don't think there is significant change of re(4) in that time window. Would you show me the revision number of if_re.c of old current? What I wonder is why re(4) is child device of pci3 on recent CURRENT whereas re(4) used to be a child device of cardbus0. Maybe imp@ know more details on this. There was a change in pccbb(4). -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081020071155.GH38923>