Problems with isrp_even message on token ring RH 5.0

[Steve Lancaster <stevelan@pogo.WV.TEK.COM>]

I've recently installed RedHat 5.0 on a pc and have been trying to use the
token ring support..

I'm using a Madge Blue+ ISA PnP token ring card..

The card is recognized by the PnP bios.. and seems to be set up ok...

When linux boots, I get:


Appletalk 0.17 for Linux NET3.035
3c59x.c:v0.46C 10/14/97 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers
/vortex.html
loading device 'eth0'...
eth0: 3Com 3c905 Boomerang 100baseTx at 0x6100, 00:60:08:3e:83:35, IRQ 11
  8K word-wide RAM 3:5 Rx:Tx split, autoselect/MII interface.
eth0: MII transceiver found at address 24.
eth0: Overriding PCI latency timer (CFLT) setting of 32, new value is 248.
ibmtr.c: v1.3.57 8/7/94 Peter De Schrijver and Mark Swanson
  modified 10/3/94 DW Morris, modified at VIA, ECP, France
  (3/9/95 F Farid and P Andre, 9/7/95 PA and 2/20/95 ML/PA/YD)
tr0: ISA P&P adapter found using irq 10, PIOaddr  a20, 16K shared RAM.
tr0: Hardware address : 00:00:F6:51:DD:16
tr0: Initial interrupt : shared RAM located at 000D02CC.
tr0: Adapter initialized and opened.
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04
tr0: adapter error: ISRP_EVEN : 04

The isrp_even message continues at a fairly high rate (about every 5 seconds
or so) until I shutdown the interface.. 

A connection established across the tr interface does, however work.

Any ideas?


Thanks..

Steve Lancaster
stevelan@pogo.wv.tek.com

P.S. I've looked at the patch sets and they seem designed for the releases
either side of RedHat's 2.0.32.. I've been reluctant to upgrade to 2.0.33
until I get some other issues settled down on the box.. but will do so if
that's believed to be the best way..