[OpenAFS] Repeated kernel oops renders AFS unusable here

[lists@naasa.net]

Hi,

I'm playing with AFS here since some time, but lately there are
some bigger problems on the clients. When having higher loads on
a Terminal-Server (Debian Sarge, vanilla 2.4.29, OpenAFS 1.3.74),
I repeatedly get stack traces and complete machine hangs. 

Any help, please? This is what I gathered, more traces are available.

ots-2:~# ksymoops -v /boot/vmlinuz-2.4.29 -V -m /boot/System.map-2.4.29
trace
Warning (multi_opt): you specified both -v and -V.  Using '-V'
ksymoops 2.4.9 on i686 2.4.29.  Options used
     -V (specified)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.29/ (default)
     -m /boot/System.map-2.4.29 (specified)

Unable to handle kernel paging request at virtual address ffffffff
f8965bc0
*pde = 00003063
Oops: 0002
CPU:    1
EIP:    0010:[<f8965bc0>]    Tainted: PF
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00210282
eax: 00000028   ebx: f8ab0b20   ecx: 00000000   edx: f6005f7c
esi: f89911e4   edi: f8aa67f0   ebp: c8ec6000   esp: c8ec7f18
ds: 0018   es: 0018   ss: 0018
Process kdeinit (pid: 23615, stackpage=c8ec7000)
Stack: f8987c40 00000000 f8ab0b20 f8974a20 c8ec6000 f8aa6760 f89911e4
f89718c8
       f8987c40 00000000 f8ab0b20 f8974a20 e89b99a0 e89b99a0 f8ab0b20
c0156918
       f8ab0b20 f8ab0b20 00000000 f8aa6760 c014dcf1 e89b99a0 e89b99a0
e89b99a0
Call Trace:    [<f8987c40>] [<f8974a20>] [<f89911e4>] [<f89718c8>]
[<f8987c40>]
  [<f8974a20>] [<c0156918>] [<c014dcf1>] [<c014de9b>] [<c010726b>]
Code: c6 05 ff ff ff ff 2a 83 c4 1c c3 90 8d 74 26 00 b8 62 93 98


>>EIP; f8965bc0 <[openafs]rxi_WritevProc+1a0/410>   <=====

>>ebx; f8ab0b20 <[openafs]debugsetsp+110b68/2230a8>
>>edx; f6005f7c <_end+35c5a870/38560954>
>>esi; f89911e4 <[openafs].rodata.end+acd1/e14d>
>>edi; f8aa67f0 <[openafs]debugsetsp+106838/2230a8>
>>ebp; c8ec6000 <_end+8b1a8f4/38560954>
>>esp; c8ec7f18 <_end+8b1c80c/38560954>

Trace; f8987c40 <[openafs].rodata.end+172d/e14d>
Trace; f8974a20 <[openafs]afs_linux_readdir+a0/7a0>
Trace; f89911e4 <[openafs].rodata.end+acd1/e14d>
Trace; f89718c8 <[openafs]osi_UFSClose+8/70>
Trace; f8987c40 <[openafs].rodata.end+172d/e14d>
Trace; f8974a20 <[openafs]afs_linux_readdir+a0/7a0>
Trace; c0156918 <d_delete+b8/c0>
Trace; c014dcf1 <vfs_unlink+181/270>
Trace; c014de9b <sys_unlink+bb/120>
Trace; c010726b <system_call+33/38>

Code;  f8965bc0 <[openafs]rxi_WritevProc+1a0/410>
00000000 <_EIP>:
Code;  f8965bc0 <[openafs]rxi_WritevProc+1a0/410>   <=====
   0:   c6 05 ff ff ff ff 2a      movb   $0x2a,0xffffffff   <=====
Code;  f8965bc7 <[openafs]rxi_WritevProc+1a7/410>
   7:   83 c4 1c                  add    $0x1c,%esp
Code;  f8965bca <[openafs]rxi_WritevProc+1aa/410>
   a:   c3                        ret
Code;  f8965bcb <[openafs]rxi_WritevProc+1ab/410>
   b:   90                        nop
Code;  f8965bcc <[openafs]rxi_WritevProc+1ac/410>
   c:   8d 74 26 00               lea    0x0(%esi),%esi
Code;  f8965bd0 <[openafs]rxi_WritevProc+1b0/410>
  10:   b8 62 93 98 00            mov    $0x989362,%eax


1 warning issued.  Results may not be reliable.
ots-2:~#


Any help would be greately appreciated,
Cajus