>Number:         10764
>Category:       kern
>Synopsis:       lots of "tlp0: receive ring overrun"
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Aug 05 12:19:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Wolfgang Rupprecht
>Release:        -current Jul 30, 2000
>Organization:
W S Rupprecht Computer Consulting, Fremont CA
>Environment:
	
System: NetBSD capsicum.wsrcc.com 1.5C NetBSD 1.5C (WSRCC) #0: Sun Jul 30 11:47:17 PDT 2000 root@capsicum.wsrcc.com:/v/src/netbsd/NetBSD-current/usr/src/sys/arch/i386/compile/WSRCC i386


>Description:

	This is mostly for completeness, in case someone else sees this too.

	When I updated the kernel a few days ago the tlp0 just started
	reporting "tlp0: receive ring overrun" approx. once a second.

	This is the same hardware that I've been using for over a year
	and the only thing tlp0 ever reported was some CRC errors under heavy
	load (under 1 CRC report per minute).

	I don't know if this is a reporting thing and tlp recently
	found its voice or if something is now locking tlp0 interrupts
	out for too long.

	The kernel config is essentially GENERIC with a few things
	commented out.  

>How-To-Repeat:

	plug a GENERIC machine int a busy ethernet.  (In my case,
	the "athome" fremont1 "cablemodem" bridged ethernet cable.

	sit there and watch.

>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted: