Reset Search
 

 

Article

Hal process crashes when accessing optic EEPROM fails continuously.

« Go Back

Information

 
TitleHal process crashes when accessing optic EEPROM fails continuously.
Symptoms
Examples of errors logged prior to system crash:
08:47:49.17 <Erro:HAL.Port.ReadOpticDDMIDataFail> Reading of DDMI data failed on the optical module in port 5.
08:47:49.17 <Erro:HAL.Port.Error> summitCardPortGetTransceiverInfoSfp: Unable to read DDMI info from Transceiver for port 1:5
08:47:49.17 <Erro:HAL.Device.Error> summitReadSfpEepromDdmi: error reading i2cdev 0x51 nbytes 128
08:47:49.17 <Erro:HAL.Device.Error> summitReadI2CDevMem: pdlib_gbic_i2c_read_nbytes failed. rc=9, port=5, addr=0x51, off=0, nbytes=128
08:47:44.17 <Erro:HAL.Port.Error> summitbcmReadGbicEeprom: Failed read port 5 eeprom 128 bytes at offset 0, fd=84 errno=110(Connection timed out)
08:47:44.10 <Erro:HAL.Port.ReadOpticDDMIDataFail> Reading of DDMI data failed on the optical module in port 4.
08:47:44.10 <Erro:HAL.Port.Error> summitCardPortGetTransceiverInfoSfp: Unable to read DDMI info from Transceiver for port 1:4
Environment
  • EXOS 22.x
  • All EXOS platforms
Cause
There may be a situation when optics module fails and EXOS can't read its EEPROM. Continuous failed read attempts cause file descriptors leak and FD exhaustion leading to system crash. File descriptors leak considered as a software defect and will be addressed via xos0075021.
Resolution
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255