>Number:         6475
>Category:       kern
>Synopsis:       
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 20 16:50:01 1998
>Last-Modified:
>Originator:     Jonathan Stone
>Organization:
	
>Release:        NetBSD 1.3H as at 1998-11-14
>Environment:
	
System: NetBSD Cuisinart.Stanford.EDU 1.3H NetBSD 1.3H (EGCS-HAIFA) #15: Sun Nov 15 17:05:22 PST 1998 jonathan@Cuisinart.Stanford.EDU:/cuisinart/compile/EGCS-HAIFA pmax


>Description:
	NetBSD's MI le driver does not report giant Ethernet packets
	as giant Ethernet packets.

>How-To-Repeat:

Connect two machines -- say,  NetBSD/pmax and a Sparc running
SunOS 4.1.3 -- to a broadcast 10Mbit ethernet segment.
Arrange for a wayward machine to send a spray of giant packets
on an Ethernet segment. (Someone else's machien did this to me today.)

Compare the logs from NetBSD-current and Solaris.

On the netbsd/pmax machine, I get:
	le0: dropping chained buffer
	le0: dropping chained buffer
	le0: dropping chained buffer
[repeated ad infinitum -- so much so i lost console access and rebooted]

On the SunOS 4.1.3_U1 sparc I get:
	le0: Receive: giant packet from 0:40:33:a0:4c:7c
	le0: Receive: STP in rmd cleared
	le0: Receive: giant packet from 55:55:55:55:55:5
	le0: Receive: STP in rmd cleared
	le0: Receive: giant packet from 55:55:55:55:55:5
	le0: Receive: STP in rmd cleared
	le0: Receive: giant packet from 55:55:55:55:55:5

assuming this problem really is due to giant-packet errors, the SunOS
message seems much more informative.

>Fix:

I dont have a lance databook. But from looking at the SunOS messages,
it looks like some chip revisions do not set STP and OFLO in quite the
way that am7990.c's input-error handler expects.
>Audit-Trail:
>Unformatted: