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

Tue Oct 17 18:26:37 PDT 2006

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
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

-----

Full dmesg(8):

NetBSD 3.1_RC3 (CFRDMDROOT.MPACPI-$Revision: 1.21.4.5 $) #9: Sat Oct 14 
21:19:14 EDT 2006

root at thunderwing:/home/nbsd/obj.i386/temp/sys/arch/i386/compile/CFRDMDROOT.MPACPI
total memory = 189 MB
avail memory = 166 MB
BIOS32 rev. 0 found at 0xfb570
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: VIA C3 Samuel 2/Ezra (686-class), 800.11 MHz, id 0x673
cpu0: features 80803035<FPU,DE,TSC,MSR,MTRR>
cpu0: features 80803035<PGE,MMX>
cpu0: features 80803035<3DNOW>
cpu0: "VIA Samuel 2"
cpu0: I-cache 64 KB 32B/line 4-way, D-cache 64 KB 32B/line 4-way
cpu0: L2 cache 64 KB 32B/line 4-way
cpu0: ITLB 128 4 KB entries 8-way
cpu0: DTLB 128 4 KB entries 8-way
cpu0: 4 page colors
acpi0 at mainbus0
acpi0: using Intel ACPI CA subsystem version 20040211
acpi0: X/RSDT: OemId <VIA601,AWRDACPI,42302e31>, AslId <AWRD,00000000>
acpi0: SCI interrupting at int 9
acpi0: fixed-feature power button present
ACPI Object Type 'Processor' (0x0c) at acpi0 not configured
acpibut0 at acpi0 (PNP0C0C): ACPI Power Button
PNP0C01 [System Board] at acpi0 not configured
PNP0A03 [PCI Bus] at acpi0 not configured
PNP0C0F [PCI interrupt link device] at acpi0 not configured
PNP0C0F [PCI interrupt link device] at acpi0 not configured
PNP0C0F [PCI interrupt link device] at acpi0 not configured
PNP0C0F [PCI interrupt link device] at acpi0 not configured
PNP0C02 [Plug and Play motherboard register resources] at acpi0 not 
configured
PNP0000 [AT Interrupt Controller] at acpi0 not configured
PNP0200 [AT DMA Controller] at acpi0 not configured
PNP0100 [AT Timer] at acpi0 not configured
PNP0B00 [AT Real-Time Clock] at acpi0 not configured
PNP0800 [AT-style speaker sound] at acpi0 not configured
npx1 at acpi0 (PNP0C04)
npx1: io 0xf0-0xff irq 13
npx1: using exception 16
fdc0 at acpi0 (PNP0700)
fdc0: io 0x3f0-0x3f5,0x3f7 irq 6 drq 2
com0 at acpi0 (PNP0501-1)
com0: io 0x3f8-0x3ff irq 4
com0: ns16550a, working fifo
com1 at acpi0 (PNP0501-2)
com1: io 0x2f8-0x2ff irq 3
com1: ns16550a, working fifo
lpt0 at acpi0 (PNP0400-1)
lpt0: io 0x378-0x37f irq 7
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: VIA Technologies product 0x0601 (rev. 0x05)
agp0 at pchb0: aperture at 0xe8000000, size 0x10000000
ppb0 at pci0 dev 1 function 0: VIA Technologies product 0x8601 (rev. 0x00)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga0 at pci1 dev 0 function 0: Trident Microsystems product 0x8500 (rev. 
0x6a)
wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
pcib0 at pci0 dev 7 function 0
pcib0: VIA Technologies VT82C686A PCI-ISA Bridge (rev. 0x40)
viaide0 at pci0 dev 7 function 1
viaide0: VIA Technologies VT82C686A (Apollo KX133) ATA100 controller
viaide0: bus-master DMA support present
viaide0: primary channel configured to compatibility mode
viaide0: primary channel interrupting at irq 14
atabus0 at viaide0 channel 0
viaide0: secondary channel configured to compatibility mode
viaide0: secondary channel interrupting at irq 15
atabus1 at viaide0 channel 1
uhci0 at pci0 dev 7 function 2: VIA Technologies VT83C572 USB Controller 
(rev. 0x1a)
uhci0: interrupting at irq 10
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 7 function 3: VIA Technologies VT83C572 USB Controller 
(rev. 0x1a)
uhci1: interrupting at irq 10
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
VIA Technologies VT82C686A SMBus Controller (miscellaneous bridge, 
revision 0x40) at pci0 dev 7 function 4 not configured
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
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
re1 at pci0 dev 17 function 0: RealTek 8139C+ 10/100BaseTX
re1: interrupting at irq 12
re1: Ethernet address 00:60:e0:e1:3e:30
re1: using 64 tx descriptors
ukphy0 at re1 phy 0: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000000, model 0x0000, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re2 at pci0 dev 18 function 0: RealTek 8139C+ 10/100BaseTX
re2: interrupting at irq 10
re2: Ethernet address 00:60:e0:e1:3e:2f
re2: using 64 tx descriptors
ukphy1 at re2 phy 0: Generic IEEE 802.3u media interface
ukphy1: OUI 0x000000, model 0x0000, rev. 0
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re3 at pci0 dev 19 function 0: RealTek 8139C+ 10/100BaseTX
re3: interrupting at irq 11
re3: Ethernet address 00:60:e0:e1:3e:2e
re3: using 64 tx descriptors
ukphy2 at re3 phy 0: Generic IEEE 802.3u media interface
ukphy2: OUI 0x000000, model 0x0000, rev. 0
ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isa0 at pcib0
pcppi0 at isa0 port 0x61
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
isapnp0: no ISA Plug 'n Play devices found
md0: internal 10500 KB image area
IPsec: Initialized Security Association Processing.
uhidev0 at uhub0 port 1 configuration 1 interface 0
uhidev0: Dell Dell USB Keyboard, rev 1.10/2.00, addr 2, iclass 3/1
ukbd0 at uhidev0
wskbd0 at ukbd0 mux 1
wskbd0: connecting to wsdisplay0
wd0 at atabus0 drive 0: <SanDisk SDCFH-2048>
wd0: drive supports 4-sector PIO transfers, LBA addressing
wd0: 1953 MB, 3970 cyl, 16 head, 63 sec, 512 bytes/sect x 4001760 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2
wd0(viaide0:0:0): using PIO mode 4, DMA mode 2 (using DMA)
atapibus0 at atabus1: 2 targets
cd0 at atapibus0 drive 1: <SAMSUNG CD-ROM  SC-148A, , B403> cdrom 
removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
cd0(viaide0:1:1): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using 
DMA)
boot device: wd0
root on md0a dumps on md0b
root file system type: ffs
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)

On Thu, 17 Aug 2006, Dag-Erling Smørgrav wrote:

> Dinesh Nair <dinesh at alphaque.com> writes:
>> i never got re(4) working, and the patch i'm currently using forces
>> the use of rl(4) instead of using re(4). using rl(4) still shows
>> media as none, but it works the way it should with packets going in
>> and out. i've yet to try dag-erling's suggestion of disabling rx and
>> tx checksums. i'll also try with the patch you sent it to see if
>> that works.
>
> If you can receive but not transmit (as I understood from other posts
> in the thread, though you never answered my question about tcpdump),
> disabling tx checksum offloading should be the *first* thing to try,
> especially as there is a known bug in some RealTek chipsets which will
> cause tx checksums to be computed incorrectly for short packets (such
> as ICMP echo replies, or TCP handshake frames).
>
> DES
> -- 
> Dag-Erling Smørgrav - des at des.no
> _______________________________________________
> freebsd-hardware at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe at freebsd.org"
>

l8*
 	-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
 	       http://www.spiritual-machines.org/

"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."