On Fri, 19 Nov 1999, J. Scott Kasten wrote:
> You're right. The entry for eth0 does not look correct. Two things you
> need to do before anyone can help you.
>
> #1 Post the output of this command:
>
> /sbin/route
>
Here it is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.10.1 * 255.255.255.255 UH 0 0 0 eth0
206.173.81.4 * 255.255.255.255 UH 0 0 0 ppp0
192.168.10.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 206.173.81.4 0.0.0.0 UG 0 0 0 ppp0
Of course, I'm not sure what I'm looking at.
> #2 Capture the output of "dmesg" into a file and chop out anything that does
> not appear to be related to networking. In particular, it should contain the
> lines from when the eth0 driver is loaded, identifying the card, etc...
>
And here it is. Does this mean what I think it does, that there is an
interrupt problem?
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x36, t=27381500.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=29500.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=7000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1500.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=28500.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=2000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=44000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=3500.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x2, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x2, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=873.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=6500.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=67000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
CSLIP: code copyright 1989 Regents of the University of California
PPP: version 2.3.7 (demand dialling)
PPP line discipline registered.
registered device ppp0
PPP BSD Compression module registered
PPP Deflate Compression module registered
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x16, t=243000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=6500.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=2500.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
eth0: Tx timed out, lost interrupt? TSR=0x43, ISR=0x3, t=1000.
PPP: ppp line discipline successfully unregistered
CSLIP: code copyright 1989 Regents of the University of California
PPP: version 2.3.7 (demand dialling)
PPP line discipline registered.
registered device ppp0
PPP BSD Compression module registered
PPP Deflate Compression module registered
> There are two common reasons for your type of problem. (And a host of less
> common ones I'm sure.) The first is not having a proper entry in the routing
> table for your NIC. The second is having the wrong interrupt or I/O space
> for your NIC. I'm going to suspect for a moment that your interrupt is
> wrong.
>
> My reasoning is this: The driver obviously loaded, so it thinks at
> some point at least that it was succesfully communicating with the
> card registers. However, not only does your TX packets show zero, but
> notice the errors figure there next to it. A TX error is usually
> recored when the driver did not get the transit finished interrupt it
> was expecting after the send. Next, notice the frames dropped on the
> RX line. Again, that's telling me that your interrupt service routine
> is not getting the packets out of the card buffer and it's over
> flowing.
>
> What make/model of card is this? What driver is it loading for it.
> (Hint: "lsmod"). The safest values for interrupt are 9 and 10 for a
> NIC. At 5, not only might the value be wrong, but you could be
> conflicting with a sound card or parallel port.
>
It's a Linksys Ether16 Lan Card. I believe the part number is LNE2000.
Driver is ne.o
There is a sound card somewhere in the machine I think, but I haven't used
it since I left Windows years ago. You think maybe I should take it out?
(Duh.)
> > Below is the output from ifconfig. What's odd is that I would expect to
> > see something other than 0 for the TX packets number for eth0 below. It
> > looks like my pinging was going out from the lo interface (see the TX
> > packets number for lo) instead of the eth0 interface.
> >
> > Am I right here, and if so, what's wrong and how can I fix it? (BTW, this
> > is RH6.1 and I've restarted the eth0 interface just to make sure.)
> >
> > eth0 Link encap:Ethernet HWaddr 00:40:05:6C:ED:A3
> > inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:2896 overruns:0 frame:0
> > TX packets:0 errors:37 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > Interrupt:5 Base address:0x300
>
> --
> J. Scott Kasten
>
Paul Foster
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
