Unable to get RealTek 8139C+ to work with re(4) under FreeBSD 6.1

[Pyun YongHyeon]

On Wed, Oct 18, 2006 at 10:55:11AM +0900, To Brian A. Seklecki wrote:
 > On Tue, Oct 17, 2006 at 09:25:52PM -0400, Brian A. Seklecki wrote:
 >  > 
 >  > Dinesh et al:
 >  > 
 >  > Did this problem ever get resolved?  I'm tracking down a very similar bug 
 >  > with an SBC - An Axiomtek SBC83672 Ver.C13.10.0.
 >  > 
 >  > Dinish: What platform are you using?  You said you had a 4x re(4) SBC, but 
 >  > never posted full dmesg(8).  Mine is a Via C3/Samuel inside an OEM network 
 >  > appliance.  URL below.  My platform is netbsd-3, but I just tried -current 
 >  > to see if recent rtl8169.c changes fix it.  No dice.
 >  > 
 >  > No dice with NetBSD -current either.
 >  > 
 >  > FreeBSD 6.1 panics at probe of re0 as you've posted.  With NetBSD, re0 
 >  > probes then fails the diagnostic function, then detatches.  re1, re2, 
 >  > re3 all then sucsessfully probe on my system, but then they show no 
 >  > media status and tcpdump(8)/arp(8) show no activity.  They're dead in 
 >  > the water.
 >  > 
 >  > There has also been some mention of the errors below on NetBSD and OpenBSD 
 >  > probably because of the bitrot/driver drift:
 >  > 
 >  > http://marc.theaimsgroup.com/?t=111658040100001&r=1&w=2
 >  > http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=26025
 >  > 
 >  > I'm gonna grab a FreeBSD 7-current snapshot boot only ISO and give it a 
 >  > go.  I see a 8139C+ fix was commited 5 weeks ago by yongar at .  Based on 
 >  > some other threads I've been reading on "8139C+ Watchdog Timeouts" and 
 >  > "Diag failed, failing to attach" related messages, I imagine FreeBSD has 
 >  > this covered.
 >  > 
 >  > re0 at pci0 dev 16 function 0: RealTek 8139C+ 10/100BaseTX
 >  > re0: interrupting at irq 5
 >  > re0: Ethernet address 00:60:e0:e1:3e:31
 >  > re0: using 64 tx descriptors
 >  > ukphy0 at re0 phy 0: Generic IEEE 802.3u media interface
 >  > ukphy0: OUI 0x000000, model 0x0000, rev. 0
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Oops, I've missed OID/model number showed on your message. Sorry.
Since ukphy(4) showed bogus model number I have no idea what PHY
hardware the NIC has. Would you show me "pciconf -lv" output?

 >  > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 >  > re: diagnostic failed, failed to receive packet in loopback mode
 >  > re0: attach aborted due to hardware diag failure
 >  > ukphy0 detached
 >  > 
 > 
 > Long ago re_diag() code was disabled by default(rev 1.68). So I think
 > you should never see the "diagnostic failed" message on FreeBSD.
 > The other odd thing I see from your demsg output is ukphy(4)
 > attachment. If you boot system with bootverbose mode ukphy(4) would
 > have printed PHY OID and model number. Please let me know the
 > OID/model number. I guess it should use rlphy(4).
 > (If you should use NetBSD you may need to define MIIVERBOSE to active
 > verbose message.)

-- 
Regards,
Pyun YongHyeon