Dialogic IMG - IMG-2020 fault with errors E_hmiExs_INVBUFLEN, API Buffer Len Overflow, and E_hmiExs_INVBUF
Table of Contents
Symptom:
Fault in IMG-2020 during configuration loading. May occur after loading an offline-prepared configuration onto an IMG-2020, or after reboot of an IMG-2020 which was fine during configuration.
We have seen a couple of versions of this error:
zHMI(F) E_hmiExs_INVBUFLEN - API Buffer Len Overflow, 608 > 512, for msg 0x83 from service cfg (693:src/zHmiExs_if.c)
ALOG(MAJ) zExsApi - E_hmiExs_INVBUF - Buffer is corrupted. allocation method = 0xffff0c02and
zHMI(F) E_hmiExs_INVBUFLEN - API Buffer Len Overflow, 544 > 512, for msg 0x83 from service cfg
ALOG(MAJ) zExsAp - WBUFCORRUPT - allocation Method on static buffer is incorrect.20c0f0f instead of deed5432Fault showed up as:
fault: #01a1cd34 @00975f48[29230] 4:$DSIExc (line = data addr)Other errors seen in fault file
00399 01/02/30 00:07:24 zHMI (F) E_hmiExs_INVBUFLEN - API Buffer Len Overflow, 608 > 512, for msg 0x83 from service cfg (693:src/zHmiExs_if.c)
00400 01/02/30 00:07:24 ALOG (MAJ) zExsApi - E_hmiExs_INVBUF - Buffer is corrupted. allocation method = 0xffff0c02
00401 01/02/30 00:07:24 ALOG (MAJ) zExsApi Crpt Buffer
0x2a46cf6c: ff ff 0c 02 2a 46 5a c3 ff ff 0c 02 ff ff 0c 02 ....*FZ.........
0x2a46cf7c: ff ff 0c 02 ff ff 0c 02 ff ff 0c 02 ff ff 0c ..................00531 01/02/30 00:08:48 ALOG (MAJ) zExsAp - WBUFCORRUPT - allocation Method on static buffer is incorrect.207e0c02 instead of deed5432
00532 01/02/30 00:08:48 ALOG (SYS) Exception:$DSIExc (line = data addr) line:0x00000004 lr:0x01a1cd34 srr0:0x00975f48 srr1:0x00029230 sp:0x3bc108e0
00533 01/02/30 00:08:48 ALOG (CRI) fault: #01a1cd34 @00975f48[29230] 4:$DSIExc (line = data addr)Solution:
Caused by reusing an IP address which was previously used for an IMG-1010 or IMG-2020 v1.1, and the old GCEMS is still configured to connect to that IMG. The GCEMS will reach out to what it thinks is its IMG-1010 and try to configure it. This causes errors in the IMG-2020, which are normally ignored, but can trigger a fault if they happen during the configuration phase.
Solution is to turn off the GCEMS, unconfigure the GCEMS (restart the GCEMS services and choose to start a new configuration), or change the IP address of the new IMG-2020 to something which is not configured in the GCEMS
Return to Documentation Home | Sangoma Support