Subject: port-i386/15756: pingflood fxp0 on tyan S2080GN locks up system
To: None <gnats-bugs@gnats.netbsd.org>
From: None <xela@mit.edu>
List: netbsd-bugs
Date: 02/27/2002 19:47:36
>Number:         15756
>Category:       port-i386
>Synopsis:       pingflood fxp0 on tyan S2080GN locks up system
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 27 16:48:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Carl Alexander
>Release:        NetBSD 1.5.2
>Organization:
Technical Education Research Center
	
>Environment:
	
System: NetBSD bellwether 1.5.2 NetBSD 1.5.2 (TERC_NETWORK_SERVER) #2: Thu Feb 21 15:50:50 EST 2002 root@foiegras:/usr/src/sys/arch/i386/compile/TERC_NETWORK_SERVER i386

>Description:

The Tyan S2080GN motherboard has two onboard ethernet ports, which
show up as fxp0 and fxp1: fxp1 is a perfectly normal fxp and works
fine, but fxp0 is a little odd:

fxp0 at pci1 dev 8 function 0: Intel i82562 Ethernet, rev 3
fxp0: interrupting at irq 11
fxp0: Ethernet address 00:e0:81:04:23:b3, 10/100 Mb/s
ukphy0 at fxp0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x00aa00, model 0x0032, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1 at pci1 dev 11 function 0: Intel i82557 Ethernet, rev 8
fxp1: interrupting at irq 5
fxp1: Ethernet address 00:e0:81:04:23:b4, 10/100 Mb/s
inphy0 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

You can configure fxp0 and it will appear to function ok until you
do something that brings a significant amount of traffic into the
interface, at which point the machine locks up tight.  The first
couple times I experienced it I was booting from the 1.5.2 install
floppies and the machine locked up part way through downloading
the sets via ftp from my local mirror.  I have subsequently been
able to consistently lock up machines by pingflooding that
interface.  Only once has it even crashed to the debugger rather
than just locking up.

I've repeated this on three different motherboards.  I've only
tried it with the interface autosensing on a 10baseT network.

	
>How-To-Repeat:
Boot NetBSD 1.5.2 on a Tyan S2080GN motherboard, configure the fxp0
interface, and pingflood or otherwise send a significant load to the
interface.

	
>Fix:
	

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