I've tested a newly built kernel.  Everything appears to be running very
stable.  dmesg(8) below.  I will attempt to deploy a system with these
changes in a "semi-production" environment to "stress test" changes..

This can be safely closed imho though.

The only lingering issue is that of whether all changes to 

src/sys/dev/ic/rtl8169.c, rtl81x9var.h, rtl81x9reg.h, rtl81x9.c, 
src/sys/dev/pci/if_re_pci.c, if_rtk_pci.c

Have been pulled into -rnetbsd-4

Revs 1.73->1.74 seem to be post 11/29/06 (when the re-branch occurred).

I can also see about testing these new versions on -rnetbsd-3.
Certainly netbsd-3 has a lot of life left to it.

~BAS

NetBSD 4.99.6 (CFRDMDROOT.MPACPI-$Revision: 1.21.4.5 $) #0: Tue Dec 19
09:34:32 EST 2006

root@thunderwing:/home/nbsd/obj.i386/20061214-2013EST/sys/arch/i386/compile/CFRDMDROOT.MPACPI
total memory = 375 MB
avail memory = 349 MB
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
BIOS32 rev. 0 found at 0xfb570
mainbus0 (root)
ACPI Error (tbxfroot-0775): No valid RSDP was found [20060217]
ACPI Exception (tbxfroot-0531): AE_NOT_FOUND, RSDP structure not found -
Flags=8 [20060217]
ACPI Exception (tbxface-0162): AE_NO_ACPI_TABLES, Could not get the RSDP
[20060217]
ACPI Exception (tbxface-0211): AE_NO_ACPI_TABLES, Could not load tables
[20060217]
ACPI: unable to load tables: AE_NO_ACPI_TABLES
cpu0 at mainbus0: (uniprocessor)
cpu0: VIA C3 Samuel 2/Ezra (686-class), 800.07 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
pnpbios0 at mainbus0: nodes 14, max len 69
npx1 at pnpbios0 index 6 (PNP0C04)
npx1: io f0-ff, irq 13
npx1: reported by CPUID; using exception 16
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
rlphy0 at re0 phy 0: Realtek internal PHY
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
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
rlphy1 at re1 phy 0: Realtek internal PHY
rlphy1: 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
rlphy2 at re2 phy 0: Realtek internal PHY
rlphy2: 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
rlphy3 at re3 phy 0: Realtek internal PHY
rlphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isa0 at pcib0
attimer0 at isa0 port 0x40-0x43: AT Timer
pcppi0 at isa0 port 0x61
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
pcppi0: attached to attimer0
isapnp0: no ISA Plug 'n Play devices found
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
md0: internal 10500 KB image area
IPsec: Initialized Security Association Processing.
uhidev0 at uhub0 port 2 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)
boot device: wd0
root on md0a dumps on md0b
root file system type: ffs


On Sat, 2006-11-04 at 16:05 +0000, tsutsui@netbsd.org wrote:
> Synopsis: re(4) fixes for 8139C+
> 
> Responsible-Changed-From-To: kern-bug-people->tsutsui
> Responsible-Changed-By: tsutsui@netbsd.org
> Responsible-Changed-When: Sun, 05 Nov 2006 01:05:03 +0900
> Responsible-Changed-Why:
> I committed fixes
> 
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: tsutsui@netbsd.org
> State-Changed-When: Sun, 05 Nov 2006 01:05:03 +0900
> State-Changed-Why:
> Could you please confirm committed fixes?
> 
> 
> 
-- 
Brian A. Seklecki <bseklecki@collaborativefusion.com>
Collaborative Fusion, Inc.