Subject: port-i386/1467: 3c509 driver (if_ep.c) panics
To: None <gnats-bugs@gnats.netbsd.org>
From: Andrew Gillham <gillhaa@ghost.whirlpool.com>
List: netbsd-bugs
Date: 09/15/1995 16:58:27
>Number:         1467
>Category:       port-i386
>Synopsis:       3c509 driver (if_ep.c) panics
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Sep 15 17:05:01 1995
>Last-Modified:
>Originator:     Andrew Gillham
>Organization:
Whirlpool Corporation
===================================================
Andrew Gillham                Whirlpool Corporation
LAN Support                 (gillhaa@whirlpool.com)
>Release:        Fri Sep 15 1995
>Environment:
	Dell Omniplex 5100 (Pentium 100 EISA/PCI)
	16MB RAM
	NCR 53C810
	Quantum 1GB
	2 x 3c509B-TPO
	NetBSD-current with 'options GATEWAY'

>Description:
	I am getting a "panic: timeout table full" when my PC is
	acting as a router, and there are large UDP transmits.
	I am routing between ep0/ep1 with a SparcStation on each
	subnet.  Running the following command on the SparcLX panics
	the NetBSD/i386 router almost immediately. (< 2seconds)
	# ./ttcp -t -s -u address.of.sparc.2
	(and './ttcp -r -s -u' on the sparc 2)

	Using TCP does not trigger a panic.  NFS mounts over UDP do
	not either.  It appears to be back-to-back UDP only.

>How-To-Repeat:
	Install 2 3c509s and use ttcp to test routing performance
	with the above commands.

>Fix:
	Unknown.  Increasing maxusers to 64 did not help.  The if_ep.c
	timeout() seems to be at fault.
>Audit-Trail:
>Unformatted: