"Transmitter access conflict" with 2.0.30

Thomas Koenig (ig25@mvmap66.ciw.uni-karlsruhe.de)
Tue, 22 Apr 1997 09:52:32 +0200


I'm currently getting lots of "eth0: transmitter access conflict" warning
messages with 2.0.30 after some very intense networking stuff
(printing a 15 Meg file from another box on a networked printer,
and copying a file of similar size from another box at the same time).

processor : 0
cpu : 586
model : Pentium 75+
vendor_id : GenuineIntel
stepping : 12
fdiv_bug : no
hlt_bug : no
fpu : yes
fpu_exception : yes
cpuid : yes
wp : yes
flags : fpu vme de pse tsc msr mce cx8
bogomips : 53.25

PCI devices found:
Bus 0, device 11, function 0:
VGA compatible controller: S3 Inc. Trio32/Trio64 (rev 64).
Medium devsel. IRQ 9.
Non-prefetchable 32 bit memory at 0xf0000000.
Bus 0, device 9, function 0:
SCSI storage controller: Adaptec AIC-7871 (rev 0).
Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=32. Min Gnt=8.Max Lat=8.
I/O at 0x6100.
Non-prefetchable 32 bit memory at 0xf4000000.
Bus 0, device 8, function 0:
Ethernet controller: 3Com 3C590 10bT (rev 0).
Medium devsel. IRQ 10. Master Capable. Latency=248. Min Gnt=3.Max Lat=8.
I/O at 0x6000.
Bus 0, device 7, function 1:
IDE interface: Intel 82371 Triton PIIX (rev 2).
Medium devsel. Fast back-to-back capable. Master Capable. Latency=32.
I/O at 0x3000.
Bus 0, device 7, function 0:
ISA bridge: Intel 82371 Triton PIIX (rev 2).
Medium devsel. Fast back-to-back capable. Master Capable. No bursts.
Bus 0, device 0, function 0:
Host bridge: Intel 82437 (rev 2).
Medium devsel. Master Capable. Latency=32.

I can no longer send out anything on the network (I presume this mail
will only make it out after a reboot :-)

I can still listen to tcpdumps on the net here, strangely enough, but
apparently I can no longer send anything out.

After a "ifconfig eth0 down", I got:

vortex_close() status e004, Tx status 88.

Hmm... "ifconfig eth0 up" plus new routes seem to work.

I also had IPIP tunneling active at the time, with a pointopoint route.

Hope this helps somebody in tracking down this problem.