Reset Search
 

 

Article

HAL process crashed with Signal 6

« Go Back

Information

 
TitleHAL process crashed with Signal 6
Symptoms
Hal crash with signal 6
The switch log show the following repeated messages:
Feb 5 18:56:14 10.10.72.201 HAL.Port: Failed to connect rtnl socket for statistics: Unspecific failure
Feb 5 18:56:14 10.10.72.201 HAL.Port: Failed to connect rtnl socket for statistics: Unspecific failure
Feb 5 18:56:14 10.10.72.201 HAL.Port: Failed to connect rtnl socket for statistics: Unspecific failure
Feb 5 18:56:14 10.10.72.201 HAL.Port: Failed to connect rtnl socket for statistics: Unspecific failure
Feb 5 18:56:15 10.10.72.201 HAL.Port: Failed to connect rtnl socket for statistics: Unspecific failure
Feb 5 18:56:15 10.10.72.201 HAL.Port: Failed to connect rtnl socket for statistics: Unspecific failure
Feb 5 18:56:18 10.10.72.201 HAL.Port: Failed to connect rtnl socket for statistics: Unspecific failure
Feb 5 18:56:18 10.10.72.201 HAL.Port: Failed to connect rtnl socket for statistics: Unspecific failure
Feb 5 18:56:18 10.10.72.201 HAL.Port: Failed to connect rtnl socket for statistics: Unspecific failure
Feb 5 18:56:42 10.10.72.201 HAL.Port: summitbcmReadGbicEeprom: Failed open fd=-1 errno=24(Too many open files) open file name(/dev/s450/gbicp49)
Feb 5 18:56:42 10.10.72.201 HAL.Port: summitbcmReadGbicEeprom: Failed open fd=-1 errno=24(Too many open files) open file name(/dev/s450/gbicp49)
Feb 5 18:56:42 10.10.72.201 HAL.Sys: Unable to update chassis odometer.
Feb 5 18:57:03 10.10.72.201 HAL.Card: Unable to set card odometer.
Feb 5 18:57:42 10.10.72.201 HAL.Sys: Unable to retrieve L1 cache correctable errors
Feb 5 18:57:42 10.10.72.201 HAL.Sys: Unable to retrieve L1 cache uncorrectable errors
Feb 5 18:57:42 10.10.72.201 HAL.Sys: Unable to retrieve L2 cache correctable errors
Feb 5 18:57:42 10.10.72.201 HAL.Sys: Unable to retrieve L2 cache uncorrectable errors
Feb 5 18:57:42 10.10.72.201 HAL.Sys: Unable to retrieve DRAM correctable errors
Feb 5 18:57:42 10.10.72.201 HAL.Sys: Unable to retrieve DRAM uncorrectable errors


Feb 5 18:57:57 10.10.72.201 Kern: Process hal pid 2093 died with signal 6
Feb 5 18:57:57 10.10.72.201 Kern:
Feb 5 18:57:57 10.10.72.201 Kern: Code:
Feb 5 18:57:57 10.10.72.201 Kern: 76eec28c 00402821 addu a1,v0,zero
Feb 5 18:57:57 10.10.72.201 Kern: 76eec290 240210aa addiu v0,zero,4266
Feb 5 18:57:57 10.10.72.201 Kern: 76eec294 0000000c syscall 0
Feb 5 18:57:57 10.10.72.201 Kern: 76eec298 <14e0000e>bne a3,zero,0x76eec2d4
Feb 5 18:57:57 10.10.72.201 Kern: 76eec29c 00000000 nop
Feb 5 18:57:57 10.10.72.201 Kern: 76eec2a0 8fb00004 lw s0,4(sp)
Environment
  • EXOS 22.3.1
  • Summit
Cause

HAL process repeatedly printed error message in BCM console leading to over usage of internal memory partition and hence HAL process got crashed.
These messages were internally stored in /scratch/intern/bcmsdk directory. When EXOS was writing these error messages in looped manner, HAL process got crashed. Developer is investigating on the root cause.

A possible reason for this behavior could be the use of unsupported optics.

Resolution

The CR# xos0069698 has a fix in the following EXOS release.

  • EXOS 22.3.1.4 patch 1-7
  • EXOS 22.4.1.4 patch 1-3
  • EXOS 22.5.1.7-patch1-2
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255