We are using the base 6.5.0 (not SR1) on an x86.  Occasionally, io-pkt-v4 will crash.  I've managed to capture slogger 
output and a .core file of the crash.  The crash happens after one and three days of operation.  We are reluctant to 
upgrade to SR1 unless it will fix the problem.  An upgrade will require a lot of regression testing and revalidation and
 we would like to avoid this.  Here is the details of the crash.  If this is a known issue please let me know how to 
avoid it.

Slogger details:
Apr 23 18:21:39    5    21     0 run fault pid 20491 tid 2 signal 11 code 1 ip 0x8085844 proc/boot/io-pkt-v4

/qpm/bin/io-pkt-v4.core:
 processor=X86 num_cpus=1
  cpu 1 cpu=586 name=Vortex86 SoC 586 F5M2S2 speed=800
   flags=0xc000001f FPU MMU CPUID RDTSC INVLPG WP BSWAP
 cyc/sec=800223700 tod_adj=1461272031260566669 nsec=163668191934739 inc=999847
 boot=2580547226 epoch=1970 intr=0
 rate=838095345 scale=-15 load=1193
   MACHINE="x86pc" HOSTNAME="localhost"
 pid=20491 parent=1 child=0 pgrp=20491 sid=1
 flags=0x003210 umask=0 base_addr=0x8048000 init_stack=0x8047ea0
 ruid=0 euid=0 suid=0  rgid=0 egid=0 sgid=0
 ign=0000000006800000 queue=ff00000000010000 pending=0000000000000000
 fds=5 threads=2 timers=1 chans=19
 canstub=0xb0320680 sigstub=0xb031a30c
 thread 1
  ip=0xb033e262 sp=0x8047dcc stkbase=0x7fc7000 stksize=528384
  state=SIGWAITINFO flags=80000000 last_cpu=1 timeout=00000000
  pri=21 realpri=21 policy=RR
 thread 2 SIGNALLED-SIGSEGV code=1 MAPERR refaddr=0 fltno=11
  ip=0x8085844 sp=0x7fa1528 stkbase=0x7fa6000 stksize=135168
  state=STOPPED flags=84000000 last_cpu=1 timeout=00000000
  pri=14 realpri=14 policy=RR