It was recently suggested that I replace my Etherexpress adaptor
with a cheap NE2000 driver, in order to fix the problems.
Fair enough, but I still having similar problems with an ISA NE2000
card. Alan Cox once told me that the cheap set was known to be good, and
it must be an interrupt conflict problem. While I disagreed with the
interrupt conflict (nothing else uses IRQ 11), I did change the IRQ from
11 to 15. I thought it fixed the problem, but it still re-occurs.
However, with 2.2.12, I get more error information:
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs 61.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy last message repeated 16 times
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy last message repeated 8 times
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy last message repeated 8 times
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy last message repeated 8 times
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy last message repeated 8 times
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy last message repeated 8 times
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy last message repeated 8 times
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy last message repeated 8 times
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: mismatched read page pointers 0 vs ff.
Sep 28 08:45:10 snoopy last message repeated 8 times
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
Sep 28 08:45:10 snoopy kernel: eth0: Too much work at interrupt, status 0xff
Sep 28 08:45:30 snoopy kernel: eth0: trigger_send() called with the transmitter busy.
Sep 28 08:45:39 snoopy kernel: eth0: Tx timed out, excess collisions. TSR=0xff, ISR=0xff, t=907.
Sep 28 08:45:39 snoopy kernel: Hw. address read/write mismap 0
Sep 28 08:45:39 snoopy kernel: Hw. address read/write mismap 1
Sep 28 08:45:39 snoopy kernel: Hw. address read/write mismap 2
Sep 28 08:45:39 snoopy kernel: Hw. address read/write mismap 3
Sep 28 08:45:39 snoopy kernel: Hw. address read/write mismap 4
Sep 28 08:45:39 snoopy kernel: Hw. address read/write mismap 5
The Ethernet adaptor just died.
Warm rebooting didn't fix my problem. It detected the adaptor
was on IRQ 3, it is actually on IRQ 15. In addition, my PPP connection
failed to start (probably because it needed IRQ 3).
I had to cold boot (as always) to fix the problem.
Any ideas? I seem to be having lots of networking problems lately.
It would be really nice if I could fix just 1...
Also, another point, with Etherexpress I get messages like:
Sep 14 15:51:31 share kernel: eth0: tx interrupt but no status
but with my NE2000 adaptor, I get messages like
Sep 28 08:45:10 snoopy kernel: eth0: unexpected TX-done interrupt, lasttx=20.
These look very similar to me. Both computers are completely different,
the only thing in common is that there are both 486.
Coincidence?
-- Brian May <bmay@csse.monash.edu.au>- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/