In the absence of a decent oops I've noticed a few other things:
ping -f from another machine will also reliably lock me up although it
takes a bit longer. Locally takes about 10-15 seconds, from another
machine takes 20-30. The other machine is running RH 6.0, 2.2.15-5 and
epic100. It's happy as a clam.
Sometimes just unplugging/replugging the eth cord and (presumably)
causing a resense will lock the machine. (not 100% reproducible)
ping -f localhost from my machine will go on forever. No problems.
In the epic.c src: #define TX_QUEUE_LEN 10
ifconfig reports: txqueuelen:100
full ifconfig:
eth0 Link encap:Ethernet HWaddr 00:E0:29:22:4F:18
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0xc000
Last thing dmesg sees:
In epic_rx(), entry 0 00401901.
eth0: interrupt interrupt=0x00240000 new intstat=0x00240000.
eth0: exiting interrupt, intr_status=0x240000.
eth0: Queued Tx packet size 42 to slot 2, flag 100000 Tx status
00000003.
eth0: interrupt interrupt=0x00210080 new intstat=0x00200000.
eth0: interrupt interrupt=0x00200000 new intstat=0x00200000.
eth0: exiting interrupt, intr_status=0x200000.
eth0: interrupt interrupt=0x00250041 new intstat=0x00240000.
-
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/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:20 EST