On Wed, Oct 13, 1999 at 01:39:52AM +0100, Alan Cox wrote:
> > eth1: Infinite loop in interrupt, status 2003.
> > eth1: transmit timed out, Tx_status 00 status 2013 Tx FIFO room 1484.
> >
> > Everything before the infinite loop is just bootup stuff. After this error,
> > eth1 is inaccessable however traffic to and from eth0 still works fine.
>
> The infinite loop is when the driver thinks that there is too much going on
> and tries to bale out and come back later.
>
> > Any ideas?
>
> Does adding
>
> options 3c509 max_interrupt_work=100
>
> to conf.modules help
Hmm that gives the following results:
argus:~# modprobe 3c509
/lib/modules/2.2.12/net/3c509.o: invalid parameter max_interrupt_work
argus:~#
This is kernel 2.2.12. Is that a 2.3.x option?
--
Shane Wegner: [EMAIL PROTECTED]
Personal website: http://www.cm.nu/~shane Fax: (604) 930-0529
PGP: keyid: 2048/1C0FFA59 ICQ UIN: 120000
Fingerprint: C6 5F B3 85 0B 11 30 F3
52 89 0C 6C 49 08 94 7B
PGP signature
