https://community.extremenetworks.com/t5/extremeswitching-exos-switch/process-hal-died/m-p/49067#M12949 Hello community,<BR /> <BR /> Two adjancies switchs rebooted signalling that the process died.<BR /> The first one said:<BR /> <BR /> 02/04/2017 09:14:07.07 <EPM.PROC_CONN_LOST> Connection lost with process hal02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66824 0320f809 jalr t9<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66820 00000000 nop<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf6681c 8f99829c lw t9,-32100(gp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66818 8fa4002c lw a0,44(sp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66814 afa70028 sw a3,40(sp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66810 <AFA20024>sw v0,36(sp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf6680c 0000000c syscall 0<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66808 24021046 addiu v0,zero,4166<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66804 8fa50004 lw a1,4(sp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> Code:<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT><BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> Process hal pid 1518 died with signal 6<BR /> 02/04/2017 09:14:00.46 <EPM.PROC_KILL> Process hal ID 1474 killed<BR /> 02/04/2017 09:14:00.46 <EPM.MSG.TIMER_THREAD> Because the Parent process (715995392) thread of process 1474, has not responded within 41 periods of 10 seconds, the process will be terminated.<BR /> <BR /> and then the second:<BR /> <BR /> 02/04/2017 09:24:06.88 <EPM.PROC_CONN_LOST> Connection lost with process hal02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66824 0320f809 jalr t9<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66820 00000000 nop<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf6681c 8f99829c lw t9,-32100(gp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66818 8fa4002c lw a0,44(sp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66814 afa70028 sw a3,40(sp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66810 <AFA20024>sw v0,36(sp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf6680c 0000000c syscall 0<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66808 24021046 addiu v0,zero,4166<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66804 8fa50004 lw a1,4(sp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> Code:<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT><BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> Process hal pid 1510 died with signal 6<BR /> 02/04/2017 09:23:59.67 <EPM.PROC_KILL> Process hal ID 1474 killed<BR /> 02/04/2017 09:23:59.67 <EPM.MSG.TIMER_THREAD> Because the Parent process (715995392) thread of process 1474, has not responded within 41 periods of 10 seconds, the process will be terminated.<BR /> <BR /> How could that be possible? Two in a row?<BR /> <BR /></EPM.MSG.TIMER_THREAD></EPM.PROC_KILL></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></AFA20024></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></EPM.PROC_CONN_LOST></EPM.MSG.TIMER_THREAD></EPM.PROC_KILL></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></AFA20024></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></EPM.PROC_CONN_LOST> Sat, 04 Feb 2017 19:08:00 GMT Julian_Eble 2017-02-04T19:08:00Z https://community.extremenetworks.com/t5/extremeswitching-exos-switch/process-hal-died/m-p/49067#M12949 Hello community,<BR /> <BR /> Two adjancies switchs rebooted signalling that the process died.<BR /> The first one said:<BR /> <BR /> 02/04/2017 09:14:07.07 <EPM.PROC_CONN_LOST> Connection lost with process hal02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66824 0320f809 jalr t9<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66820 00000000 nop<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf6681c 8f99829c lw t9,-32100(gp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66818 8fa4002c lw a0,44(sp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66814 afa70028 sw a3,40(sp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66810 <AFA20024>sw v0,36(sp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf6680c 0000000c syscall 0<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66808 24021046 addiu v0,zero,4166<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> 2cf66804 8fa50004 lw a1,4(sp)<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> Code:<BR /> 02/04/2017 09:14:00.90 <KERN.ALERT><BR /> 02/04/2017 09:14:00.90 <KERN.ALERT> Process hal pid 1518 died with signal 6<BR /> 02/04/2017 09:14:00.46 <EPM.PROC_KILL> Process hal ID 1474 killed<BR /> 02/04/2017 09:14:00.46 <EPM.MSG.TIMER_THREAD> Because the Parent process (715995392) thread of process 1474, has not responded within 41 periods of 10 seconds, the process will be terminated.<BR /> <BR /> and then the second:<BR /> <BR /> 02/04/2017 09:24:06.88 <EPM.PROC_CONN_LOST> Connection lost with process hal02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66824 0320f809 jalr t9<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66820 00000000 nop<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf6681c 8f99829c lw t9,-32100(gp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66818 8fa4002c lw a0,44(sp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66814 afa70028 sw a3,40(sp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66810 <AFA20024>sw v0,36(sp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf6680c 0000000c syscall 0<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66808 24021046 addiu v0,zero,4166<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> 2cf66804 8fa50004 lw a1,4(sp)<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> Code:<BR /> 02/04/2017 09:24:00.10 <KERN.ALERT><BR /> 02/04/2017 09:24:00.10 <KERN.ALERT> Process hal pid 1510 died with signal 6<BR /> 02/04/2017 09:23:59.67 <EPM.PROC_KILL> Process hal ID 1474 killed<BR /> 02/04/2017 09:23:59.67 <EPM.MSG.TIMER_THREAD> Because the Parent process (715995392) thread of process 1474, has not responded within 41 periods of 10 seconds, the process will be terminated.<BR /> <BR /> How could that be possible? Two in a row?<BR /> <BR /></EPM.MSG.TIMER_THREAD></EPM.PROC_KILL></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></AFA20024></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></EPM.PROC_CONN_LOST></EPM.MSG.TIMER_THREAD></EPM.PROC_KILL></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></AFA20024></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></KERN.ALERT></EPM.PROC_CONN_LOST> Sat, 04 Feb 2017 19:08:00 GMT https://community.extremenetworks.com/t5/extremeswitching-exos-switch/process-hal-died/m-p/49067#M12949 Julian_Eble 2017-02-04T19:08:00Z https://community.extremenetworks.com/t5/extremeswitching-exos-switch/process-hal-died/m-p/49068#M12950 Please contact GTAC. There is a great team what will help . Sat, 04 Feb 2017 19:18:00 GMT https://community.extremenetworks.com/t5/extremeswitching-exos-switch/process-hal-died/m-p/49068#M12950 Zdeněk_Pala 2017-02-04T19:18:00Z https://community.extremenetworks.com/t5/extremeswitching-exos-switch/process-hal-died/m-p/49069#M12951 Need to check complete show tech and the current version of software running at this moment on this device. If possible then do provide us the same here else can contact our GTAC support team working 24/7. Sun, 05 Feb 2017 02:04:00 GMT https://community.extremenetworks.com/t5/extremeswitching-exos-switch/process-hal-died/m-p/49069#M12951 Tripathy__Priya 2017-02-05T02:04:00Z