[vortex] causes 3c905c jitter ???

[Stefan Doehla]

At the end of my mail is something about my settings ...

>>Can the 3com networkcard lock the PCI bus for some microseconds? Uses it 
>>a fifo that's not checked before writing (due to performance gains)?
>>
> 
> What chip, and what driver version?
> 
> You can change various settings to limit the PCI burst size, but I don't
> know what you are seeing that's a problem.
> 

=========================

root@labpc7:/var/tmp# ./vortex-diag -aa
vortex-diag.c:v2.05 5/15/2001 Donald Becker (becker@scyld.com)
  http://www.scyld.com/diag/index.html
Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xa400.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
Initial window 7, registers values by window:
   Window 0: 0000 0000 d93f 0000 e3e3 00bf ffff 0000.
   Window 1: FIFO FIFO 0700 0000 0000 007f 0000 2000.
   Window 2: 0100 9802 1d07 0000 0000 0000 0052 4000.
   Window 3: 0000 0180 05ea 0020 000a 0800 0800 6000.
   Window 4: 0000 0000 0000 0cfa 0001 8880 0200 8000.
   Window 5: 1ffc 0000 0000 0600 0807 06ce 06c6 a000.
   Window 6: 0000 0000 0000 c901 0100 d79a 34ce c000.
   Window 7: 0000 0000 0000 0000 0000 0000 0000 e000.
Vortex chip registers at 0xa400
   0xA410: **FIFO** 00000000 0000000d *STATUS*
   0xA420: 00000020 00000000 00080000 00000004
   0xA430: 00000000 14c7eb39 14fe5900 00080004
  Indication enable is 06c6, interrupt enable is 06ce.
  No interrupt sources are pending.
  Transceiver/media interfaces available:  100baseTx 10baseT.
Transceiver type in use:  Autonegotiate.
  MAC settings: full-duplex.
  Station address set to 00:01:02:98:07:1d.
  Configuration options 0052.

=======================
root@labpc7:/var/tmp# lspci -s 0c -vvvxxx
00:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] 
(rev 74)
	Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- 
<MAbort- >SERR- <PERR-
	Latency: 32 (2500ns min, 2500ns max), cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at a400
	Region 1: Memory at fa000000 (32-bit, non-prefetchable)
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=2 PME-
00: b7 10 00 92 17 00 10 02 74 00 00 02 08 20 00 00
10: 01 a4 00 00 00 00 00 fa 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 b7 10 00 10
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0b 01 0a 0a
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 02 fe
e0: 00 40 00 b7 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

=========================

I hope this information is enough ...

Is there any option I can use to make the card very very conseravtive ...


Thanks
Stefan