>Number:         28870
>Category:       port-macppc
>Synopsis:       Tulip driver generating "tlp0: receive ring overrun" messages, severe network slowdown
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    port-macppc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jan 05 03:06:00 +0000 2005
>Originator:     Patrick Cronin
>Release:        NetBSD-2.0
>Organization:
>Environment:
NetBSD elixir 2.0 NetBSD 2.0 (GENERIC) #0: Tue Jan 5 03:03:55 UTC 2005 builds@build:/big/builds/ab/netbsd-2-0-RELEASE/macppc/200411300000Z-obj/big/builds/ab/netbsd-2-0-RELEASE/src/sys/arch/macppc/compile/GENERIC macppc
>Description:
I recently installed NetBSD-2.0/macppc on a PowerMac 6500/300.

When I started using pkg_add to install packages from ftp.netbsd.org, I was getting many (hundreds or even thousands) messages reading:

tlp0: receive ring overrun

When the tlp0 device is initially brought up, I can use the network with no problems. Transfer rates start at about 250KB/s (10base-T).  After an estimated 10MB goes through the tlp0 device, I start to get "tlp0: receive ring overrun" first intermittently, then soon with every blink of the ethernet light comes another of the same message.

If I bring the interface down and back up, the problem goes away until I get another 10MB or so through the device.  Then, the messages start coming back again.

I've looked around on google and in the netbsd newsgroups, and see that this problem is not new (http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=10764) (kern/10764). I found Andreas Johansson's patch for the tulip driver from 10 November 2000, and manually applied it to the tulip.c file in the syssrc.tgz for NetBSD-2.0, recompiled the kernel, and copied the newly created kernel to /netbsd.  The new kernel boots and works fine, but the tlp0 messages still come with the same patterns as they did before.

Apple's website for this model:
http://docs.info.apple.com/article.html?artnum=112410

Network card is: Farallon 10/100Base-TX Ether PCI
with a digital (dec) 21143-PC chip

dmesg output:

NetBSD 2.0 (GENERIC) #0: Wed Jan  5 03:03:55 UTC 2005
	builds@build:/big/builds/ab/netbsd-2-0-RELEASE/macppc/200411300000Z-obj/big/builds/ab/netbsd-2-0-RELEASE/src/sys/arch/macppc/compile/GENERIC
total memory = 128 MB
avail memory = 117 MB
mainbus0 (root)
cpu0 at mainbus0: 603ev (Revision 2.1), ID 0 (primary)
cpu0: HID0 90c001<DOZE,DPM,ICE,DCE,NOPTI>
cpu0bandit0 at mainbus0
pci0 at bandit0 bus 0
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 11 function 0
pchb0: Apple Computer Bandit Host-PCI Bridge (rev. 0x03)
tlp0 at pci0 dev 14 function 0: DECchip 21143 Ethernet, pass 3.0
tlp0: interrupting at irq 25
tlp0: Ethernet address 00:00:c5:53:63:67
tlp0: 21143 reset block
tlp0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
obio0 at pci0 dev 16 function 0: addr 0xf3000000
mesh0 at obio0 offset 0x10000 irq 12: 50MHz, SCSI ID 7
scsibus0 at mesh0: 8 targets, 8 luns per target
zsc0 at obio0 offset 0x13000: irq 15,16
zstty0 at zsc0 channel 0
zstty1 at zsc0 channel 1
awacs at obio0 offset 0x14000 not configured
swim3 at obio0 offset 0x15000 not configured
nvram0 at obio0 offset 0x60000
wdc0 at obio0 offset 0x20000 irq 13: DMA transfer
atabus0 at wdc0 channel 0
adb0 at obio0 offset 0x16000 irq 18: 2 targets
aed0 at adb0 addr 0: ADB Event device
akbd0 at adb0 addr 2: extended keyboard
wskbd0 at akbd0: console keyboard
ams0 at adb0 addr 3: 1-button, 100 dpi mouse
wsmouse0 at ams0 mux 0
ofb0 at pci0 dev 18 function 0: ATI Technologies 3D Rage I/II
ofb0: 1024 x 768, 8bpp
wsdisplay0 at ofb0 kbdmux 1: console (std, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
scsibus0: waiting 2 seconds for devices to settle...
cd0 at scsibus0 target 3 lun 0: <MATSHITA, CD-ROM CR-8024, 2.0f> cdrom removable
sd0 at scsibus0 target 5 lun 0: <IOMEGA, ZIP 100, E.08> disk removable
sd0: drive offline
wd0 at atabus0 drive 0: <QUANTUM FIREBALL ST6400A>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 6149 MB, 13328 cyl, 15 head, 63 sec, 512 bytes/sect x 12594960 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
wd0(wdc0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
boot device: wd0
root on wd0a dumps on wd0b
WARNING: clock lost 17628 days, using FS time -- CHECK AND RESET THE DATE!
root file system type: ffs
>How-To-Repeat:
Just use the network to receive about 10MB of data, and the messages will come without fail.
>Fix: