Oops message from cvs process

[Satya Prasad DV]

hi,
  We are using the RHL 7.1 with cvs software version cvs-1.11.1p1
patched to get additional info for logging using AlternateInfo=yes in
config. We had no trouble with this s/w for over one year. Recently we
upgraded the server by increasing RAM to 512M and adding scsi drive for
the cvs repository partition. 

After this, the server started spewing out lots of Oops messages after
7-8 days of operation. If I reboot the machine the problem disappears for
a while and starts again.The oops seems to be result of the cvs process.
Iam listing the ksymoops output below.

Kindly help me to locate the problem.

Thanks in advance,
--
Satya Prasad

OOPS output is  BELOW
ksymoops 2.4.0 on i686 2.4.2-2. 
Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.2-2/ (default)
     -m /usr/src/linux-2.4/System.map
(specified)

Warning (compare_maps): ksyms_base symbol
__VERSIONED_SYMBOL(shmem_file_setup) not found in System.map. 
Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol
scsi_logging_level_R__ver_scsi_logging_level not found in
System.map.  Ignoring ksyms_base entry
Warning (compare_maps): mismatch on symbol usb_devfs_handle  ,
usbcore says e0860da0, /lib/modules/2.4.2-2/kernel/drivers/usb/usbcore.o
says e08608c0.  Ignoring
/lib/modules/2.4.2-2/kernel/drivers/usb/usbcore.o entry
 Unable to handle kernel paging request at virtual address
00800010
 c0146aec
 Oops: 0000
 CPU:    0
 EIP:    0010:[__mark_inode_dirty+28/112]
 EIP:    0010:[<c0146aec>]
Using defaults from ksymoops -t elf32-i386 -a i386
 EFLAGS: 00010206
 eax: 00004000   ebx: 00800000   ecx:
00000000   edx: d3b1fd74
 esi: d3b1fc80   edi: 00000000   ebp:
dc533a00   esp: c5031f84
 ds: 0018   es: 0018   ss: 0018
 Process cvs (pid: 22254, stackpage=c5031000)
 Stack: 00000001 dc533a00 00000000 0000000b bfffefb8 c0131be1
00000000 dc533a00 
        00000000 dc533a00 080e94c0
c0131c43 dc533a00 c35efb80 c5030000 c0108f2b 
        0000000b 00000000 402149e4
080e94c0 0000000b bfffefb8 00000006 c010002b 
 Call Trace: [kmap_high+65/352] [kmap_high+163/352]
[do_signal+667/672] [startup_32+43/313] 
 Call Trace: [<c0131be1>] [<c0131c43>]
[<c0108f2b>] [<c010002b>] 
 Code: 39 6b 10 75 f3 85 db 74 33 8b 2c 24 85 ed 74 14 8b 03 89 02

>>EIP; c0146aec <fcntl_dirnotify+9c/150>  
<=====
Trace; c0131be1 <filp_close+41/60>
Trace; c0131c43 <sys_close+43/50>
Trace; c0108f2b <system_call+33/38>
Trace; c010002b <startup_32+2b/139>
Code;  c0146aec <fcntl_dirnotify+9c/150>
00000000 <_EIP>:
Code;  c0146aec <fcntl_dirnotify+9c/150>  
<=====
   0:   39 6b
10                 
cmp    %ebp,0x10(%ebx)   <=====
Code;  c0146aef <fcntl_dirnotify+9f/150>
   3:   75
f3                    
jne    fffffff8 <_EIP+0xfffffff8> c0146ae4
<fcntl_dirnotify+94/150>
Code;  c0146af1 <fcntl_dirnotify+a1/150>
   5:   85
db                    
test   %ebx,%ebx
Code;  c0146af3 <fcntl_dirnotify+a3/150>
   7:   74
33                    
je     3c <_EIP+0x3c> c0146b28
<fcntl_dirnotify+d8/150>
Code;  c0146af5 <fcntl_dirnotify+a5/150>
   9:   8b 2c
24                 
mov    (%esp,1),%ebp
Code;  c0146af8 <fcntl_dirnotify+a8/150>
   c:   85
ed                    
test   %ebp,%ebp
Code;  c0146afa <fcntl_dirnotify+aa/150>
   e:   74
14                    
je     24 <_EIP+0x24> c0146b10
<fcntl_dirnotify+c0/150>
Code;  c0146afc <fcntl_dirnotify+ac/150>
  10:   8b
03                    
mov    (%ebx),%eax
Code;  c0146afe <fcntl_dirnotify+ae/150>
  12:   89
02                    
mov    %eax,(%edx)


3 warnings issued.  Results may not be reliable.

 Pls. enlighten me how to find the source of this problem and
the fix for it .