Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!rice!sun-spots-request
From: ece!mikulska@ucsd.edu (Margaret Mikulska)
Newsgroups: comp.sys.sun
Subject: Re: Problem with le0 on 4/330 CPU board
Keywords: SunOS
Message-ID: <5427@brazos.Rice.edu>
Date: 3 Mar 90 03:44:50 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 24
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n66
X-Sun-Spots-Digest: Volume 9, Issue 63, message 6

In article <5406@brazos.Rice.edu> ehrlich@shire.cs.psu.edu (Daniel Ehrlich) writes:
>X-Sun-Spots-Digest: Volume 9, Issue 66, message 4
>
>We just upgraded a Sun 4/260 to a Sun 4/360 and have started seeing the
>following in our system log.  The system seems to recover from this, but
>we were wondering if anyone could shed some light on why it was happening
>and if there was anything that could be done about it.
>
>Mar  1 09:02:32 shire vmunix: le0: Transmission stopped
>Mar  1 09:02:32 shire vmunix: le0: csr: 2e3<TINT,INTR,INEA,RXON,STRT,INIT,>

This is a known bug (one of many) in the Lance ethernet chip. This
particular bug results from transmit memory underflow. Bug ID: 1029247,
1019513, 1029316.  A patch is available from Sun; it's a replacement for
the kernel module "if_le.o", for sun3x, sun4 and sun4c architectures, for
SunOS 4.0.3.

Supposedly, this bug is fairly harmless (doesn't crash the system) and
affects mainly performance.

Margaret Mikulska
University of California, San Diego
Dept. of Electrical and Computer Engineering
mikulska@ece.ucsd.edu