ipfrag_lock related lockup

From: Andreas Ehliar (ehliar@lysator.liu.se)
Date: Wed Jun 21 2000 - 10:08:15 EST


Hi.

2.4.0test1-riel-ac22 seems to lockup for me. It only happens after starting
knfsd. The lockup doesn't happen immediately after starting knfsd
though. (The server is not heavily utilized, it only exports my home directory
to one machine.)

The lockup has only occured while running a kernel with SMP support.
I haven't done any heavy testing while running a non SMP kernel though.

Anyway, with the help of sysrq-p I got the EIP (0xc024cbb0) and this is
what turned up:

(gdb) x/5i 0xc024cbb0
0xc024cbb0 <stext_lock+24024>: cmpb $0x0,0xc02e342c
0xc024cbb7 <stext_lock+24031>: repz nop
0xc024cbb9 <stext_lock+24033>: jle 0xc024cbb0 <stext_lock+24024>
0xc024cbbb <stext_lock+24035>: jmp 0xc020e763 <ip_defrag+43>
0xc024cbc0 <stext_lock+24040>: call 0xc010ac84 <__read_lock_failed>
(gdb) x/5i 0xc020e763
0xc020e763 <ip_defrag+43>: lock decb 0xc02e342c
0xc020e76a <ip_defrag+50>: js 0xc024cbb0 <stext_lock+24024>
0xc020e770 <ip_defrag+56>: mov 0xc02e3430,%eax
0xc020e775 <ip_defrag+61>: cmp 0xc02e3420,%eax
0xc020e77b <ip_defrag+67>: jle 0xc020e782 <ip_defrag+74>
(gdb) x/x 0xc02e342c
0xc02e342c <ipfrag_lock>: 0x00000001

And here I'm afraid I don't have enough skill to continue. ip_fragment.c
is clearly beyond me.

Some more information:
The machine in question is a dual PII 266. I have a 3c905B and two rt8139
cards in it. The NFS client is connected to one of the rt8139 cards.
The machine is also acting as a masquerading firewall. If there is any
interest I can try to reproduce the bug without any firewall rules enabled.

-
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 : Fri Jun 23 2000 - 21:00:22 EST