I'm having severe hardlocks with 2.5.69-mm3 when mounting an NFS volume
from one of my NFS servers. I think this is related to iptables, but
while investigating, I found the following messages on my dmesg ring:
spurious 8259A interrupt: IRQ7.
eth0: Setting full-duplex based on MII #0 link partner capability of
01e1.
eth0: Transmit error, Tx status register 90.
Flags; bus-master 1, dirty 923(11) current 927(15)
Transmit list 0f37f980 vs. cf37f8e0.
0: @cf37f200 length 80000036 status 00010036
1: @cf37f2a0 length 80000036 status 00010036
2: @cf37f340 length 80000036 status 00010036
3: @cf37f3e0 length 80000036 status 00010036
4: @cf37f480 length 80000036 status 00010036
5: @cf37f520 length 80000036 status 00010036
6: @cf37f5c0 length 80000036 status 00010036
7: @cf37f660 length 80000036 status 00010036
8: @cf37f700 length 80000036 status 80010036
9: @cf37f7a0 length 80000036 status 00010036
10: @cf37f840 length 80000036 status 00010036
11: @cf37f8e0 length 80000036 status 00010036
12: @cf37f980 length 80000036 status 00000036
13: @cf37fa20 length 80000036 status 00000036
14: @cf37fac0 length 80000036 status 80000036
15: @cf37fb60 length 80000036 status 00010036
eth0: Too much work in interrupt, status e401.
I have no idea what does this mean...
-- Please AVOID sending me WORD, EXCEL or POWERPOINT attachments. See http://www.fsf.org/philosophy/no-word-attachments.html Linux Registered User #287198- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/