[tulip] PCI bus fatal errors with Linksys LNE100tx

[Mario Simoni]

> > > You have an invalid option in /etc/conf.modules  (/etc/modules.conf).
> >
> > This may be the problem, because I originally tried to configure the ethernet card
> > using linuxconf and it placed the following lines in my conf.modules file:
> >
> > alias eth0 tulip
> > options eth0 irq=11 io_addr=0xfc00
>
> This is exactly your problem.
> The "irq=" and "io=" options are only for ISA drivers.

This did fix my problem and I now have my network card working. However, when I look at
the /var/log/messages file I hundreds of lines of PCI Fatal Bus errors of different
types as shown below.  This is the point in the file where it begins to  give  the
error messages after booting up. After this there are hundreds more messages of the
same types listed below.

Sep 20 22:36:22 rivendel kernel: tulip.c:v0.92i 7/31/2000  Written by Donald Becker
<becker@scyld.com>
Sep 20 22:36:22 rivendel kernel:   http://www.scyld.com/network/tulip.html
Sep 20 22:36:22 rivendel kernel: eth0: ADMtek Comet rev 17 at 0xc2852c00,
00:20:78:1E:53:F4, IRQ 11.
Sep 20 22:36:22 rivendel kernel: eth0:  MII transceiver #1 config 1000 status 786d
advertising 01e1.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc66e010.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc27e014.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc67e050.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc67e050.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc26e010.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc67e014.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc67e050.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc67e050.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc16e010.
Sep 20 22:36:22 rivendel kernel: eth0: PCI Fatal Bus Error, fc67e050.
Sep 20 22:36:23 rivendel kernel: eth0: PCI Fatal Bus Error, fc66e010.

Occasionally I see the following messages mixed in with the PCI Fatal bus errors

Sep 20 22:50:01 rivendel kernel: eth0: Too much work during an interrupt,
csr5=0xfc174014.
Sep 20 22:50:01 rivendel kernel: eth0: Re-enabling interrupts, fc66c810


The output of 'tulip-diag -m -e -a' is

[root@rivendel /root]# tulip-diag -a -m -e
tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xfc00.
ADMtek AL985 Centaur-P chip registers at 0xfc00:
  fff98000 ffffffff ffffffff 00e3f800 00e3fa00 fc06c012 ff9f0115 fffe4010
  fffe0000 fff097fe 00000000 fffe0000 00000000 00000200 00000000 c40ffec8
  0006c812 a04c0004 00000000 00e3f9f0 f0000000 fffff453 00000000 00000000
  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Stopped'.
  The transmit threshold is 128.
 Interrupt sources are pending!  CSR5 is fc06c812.
   Tx complete indication.
   Link passed indication.
   Timer expired indication.
   Early Rx indication.
 The Comet MAC registers are 1e782000 fffff453 filter 8000000000000000.
 EEPROM size is 8.
  Ethernet MAC Station Address 00:20:78:1e:53:f4.
  Default connection type 'Autosense'.
  PCI IDs Vendor 1317 Device 0985  Subsystem 1317 0574
  PCI min_grant 255 max_latency 255.
  CSR18 power-up setting 0xa04c****.
 MII PHY found at address 1, status 0x786d.
 MII PHY found at address 2, status 0x786d.
 MII PHY found at address 3, status 0x786d.
 MII PHY found at address 4, status 0x786d.

I have the options for tulip set to options=9 debug=3

What do these errors mean? Is it hurting the performance of my card at all?

Thanks for the help.

Mario