On Sat, 3 Jul 1999, John Pearson wrote:
> On Fri, Jul 02, 1999 at 08:41:47PM -0500, Robert Rati wrote
> > The message in /var/log/syslog said this:
> > Jul 2 20:27:08 Obereon kernel: eth0: Tx timed out, lost interrupt?
> > TSR=0x1, ISR=0x2, t=3500.
> > Jul 2 20:27:18 Obereon kernel: eth0: Tx timed out, lost interrupt?
> > TSR=0x1, ISR=0x2, t=1000.
> > Jul 2 20:27:28 Obereon kernel: eth0: Tx timed out, lost interrupt?
> > TSR=0x1, ISR=0x3, t=1000.
> > Jul 2 20:27:48 Obereon last message repeated 2 times
> > Jul 2 20:27:55Obereon
> > ypbind[157]: broadcast: RPC: Timed out.
> >
> > This message can't mean what it seems. A lost interrupt? That's not
> > possible is it? I have never encountered this thing before. Can anyone
> > give some insite?
> >
>
> Your NIC driver is sending stuff to your NIC and expects to receive an
> interrupt down the track (probably to say that it has finished), but the
> interrupt never arrives.
>
> In approximately descending order of plausability, you either:
> - Have configured the NIC driver to use the wrong IRQ; or
> - Have a broken NIC; or
> - Have configured the NIC driver to use the wrong I/O address; or
> - Are using the wrong module for your NIC.
>
> If it's a PCI card, then settings probably *aren't* the problem.
I know the nic works because I can still use it in winblows. The card is
detected when I give it an irq, or atleast it is said to be detected
correctly. The werid thing is, it stopped being detected when I just gave
it the io port. It used to just need the io port, and it would find the
irq itself and work just fine. Now I have to give it the irq also, and it
says it finds it but it doesn't work. My nic is an ISA Linksys and I just
use the ne drive for it. I've had it working before and it still works in
winblows, so I don't think it's the settings or the card. It's got an
EEPROM on it, and the eeprom is set to use IRQ 10 and io 0x240.
Rob
