Re: RX overrun with 3COM 3c982

Donald Becker <[email protected]>
Newsgroups gmane.linux.drivers.vortex.devel
Message-ID <[email protected]>
On Mon, 18 Nov 2002, Claude Pignol wrote:
> >>>Hmmm, this might be doing long PCI bursts, not leaving enough for the
> >>>Ethernet.  If that's the case, the solution is to:
> >>>  Change the Min-grant / Max-Latency PCI settings
> >>>  Set the PCI bursts to much longer values, although the '982 has
> >>>    reasonable defaults.  The registers to change are the
> >>>    UpBurstThreshold at offset 0x3e and
> >>>    UpPriorityThreshold, offset 0x3c, default 4*32 = 128 bytes.

OK, more work, and an updated vortex-diag just for this:
  ftp://ftp.scyld.com/pub/diag/vortex-diag.c

Try setting
  -G 512

________________
vortex-diag.c:v2.11 11/19/2002

Corrected the Tx and Rx FIFO priority levels output when the '-g' flag
is passed.

Allow changing the Rx FIFO priority level with the -G <threshold-bytes> flag.

Modified the EEPROM size detection to work with chips where the EEPROM
command is in bits 9:8 rather than 7:6.  This isn't documented anywhere
(in fact a longer address is documented as straddling rather than moving
the command) but it does occur on a few chips.
________________


-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993

_______________________________________________
vortex mailing list
[email protected]
http://www.scyld.com/mailman/listinfo/vortex
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.