[vortex] RX overrun with 3COM 3c982

[Donald Becker]

On Tue, 19 Nov 2002, Claude Pignol wrote:
> Donald Becker wrote:
> >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

What are the settings.  This is really starting to look like a
bug-hogging issue, or the 3Ware card sometimes holding the bus as a
slave-target.

> >>>>> 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
..
> I try the new vortex-diag:
> Registers berfore -G512

Could you show this with '-g'?
I know that I should make that the default for the Cyclone.

> 0x2410: **FIFO** 00000000 0000000f *STATUS*
> 0x2420: 00000020 3775daf0 00080000 00001404
> 0x2430: 00000000 0608f9f8 3775d8b0 00080004

Priority 128..

> Registers after the RX priority to 512 bytes
> 0x2430: 00000000 c3123cee 3775d990 00080010

Good, priority at 512 bytes.

> Error ratio: ( 127616 -123204)/(534880121-468076386)=.000066
> For the same period an interface with the default value has a ratio .00018
> It seems that it goes in the right direction (there is no interface with 
> a ratio < .00012 with the default value).

This really points to the 3Ware.

Try -G 1024...

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