2.4.24 Kernel panic (patch 2.4.24-1)
<oops - forgot to attach the back trace>
The following has been seen for some time on an intermittent basis. less than 1:20 runs. Having trouble debugging it so I added some code to panic.c:panic() to abort() and dump core. Also attached is a back trace from that.
Kernel panic: handle_trap - failed to wait at end of syscall, errno = 2,
status = 383
appreciate any tips or tricks to get more information about this problem.
I have a core if that helps.
regards, Giovanni
ps. The kernel I am running is slightly modified but I do not believe that is related. I will look more on a vanilla kernel just to be sure.
(gdb) bt
#0 0xa01643d1 in kill ()
at /localdisk/builds/3pc/2.4.22-i686sim/2.4.22/include/linux/if_vlan.h:122
#1 0xa018cbcb in raise ()
at /localdisk/builds/3pc/2.4.22-i686sim/2.4.22/include/linux/if_vlan.h:122
#2 0xa01646bd in abort ()
at /localdisk/builds/3pc/2.4.22-i686sim/2.4.22/include/linux/if_vlan.h:122
#3 0xa00d01d5 in handle_trap () at process.c:88
#4 0xa00d042c in userspace (regs=0xade0827c) at process.c:166
#5 0xa00d0bee in fork_handler (sig=10) at process_kern.c:102
#6 <signal handler called>
#7 0xa01643d1 in kill ()
at /localdisk/builds/3pc/2.4.22-i686sim/2.4.22/include/linux/if_vlan.h:122#8 0xa00d4728 in os_usr1_process (pid=Cannot access memory at address 0x8 ) at process.c:95