No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

How to Clear the S2600 R2 Memory Leakage Alarm on the TLV Message Module

Publication Date:  2012-07-22 Views:  48 Downloads:  0
Issue Description
Under certain circumstances, the command sent by an S2600 module to release memory fails to be executed, finally resulting in an alarm that the memory usage exceeds the threshold. In this example, the memory usage reaches 83%.
Phenomenon 1:

Phenomenon 2:
MML>mem 1002                    
Pid = 1002, Memory = 522740(Byte), 289 = Malloc(159726787) - Free(159726498)
Index  Size(Byte) Address(HEX)      Type  Function(Line)         Time
    1       8000  10005126000          2  MSGOBJ_GetMem:583      2010-4-15 3:15:11
    2       8000  100054bc000          2  MSGOBJ_GetMem:583      2010-4-15 3:15:52
    3       8000  10005866000          2  MSGOBJ_GetMem:583      2010-4-15 3:15:1
    4       8000  10006550000          2  MSGOBJ_GetMem:583      2010-4-15 3:37:26
    5       8000  10006824000          2  MSGOBJ_GetMem:583      2010-3-25 1:51:33
    6       8000  100068c0000          2  MSGOBJ_GetMem:583      2010-4-15 3:15:11
7       8000  10006d58000          2  MSGOBJ_GetMem:583      2010-3-25 1:45:55
    8       8000  10006f62000          2  MSGOBJ_GetMem:583      2010-3-25 1:45:55
    9       8000  10007d28000          2  MSGOBJ_GetMem:583      2010-3-25 1:45:55
   10       8000  10007dde000          2  MSGOBJ_GetMem:583      2010-3-25 1:51:33
   11       8000  10008132000          2  MSGOBJ_GetMem:583      2010-3-25 2:0:36
   12       8000  10008672000          2  MSGOBJ_GetMem:583      2010-3-25 2:0:36
   13       8000  10008904000          2  MSGOBJ_GetMem:583      2010-3-25 1:45:55
   14       8000  10008cc4000          2  MSGOBJ_GetMem:583      2010-4-15 3:10:34
   15       8000  10008d9e000          2  MSGOBJ_GetMem:583      2010-3-25 1:51:33
   16       8000  10009dba000          2  MSGOBJ_GetMem:583      2010-3-25 1:51:33
   17        122  10009dcb780          2  MSGOBJ_Create:59       2010-4-15 3:16:54
   18        122  10009dcb900          2  MSGOBJ_Create:59       2010-4-15 3:13:18
   19        122  10009dcb980          2  MSGOBJ_Create:59       2010-4-15 3:13:18
   20        122  10009dcbb80          2  MSGOBJ_Create:59       2010-4-22 2:28:22
   21        122  10009dcbc00          2  MSGOBJ_Create:59       2010-4-15 3:10:4
   22        122  10009dcbc80          2  MSGOBJ_Create:59       2010-4-15 3:13:18
   23        122  10009dcbd80          2  MSGOBJ_Create:59       2010-4-15 3:15:52
   24        122  10009dcbe00          2  MSGOBJ_Create:59       2010-4-15 3:10:34
   25        122  10009dcbe80          2  MSGOBJ_Create:59       2010-4-15 3:15:1
   26        122  10009dcbf00          2  MSGOBJ_Create:59       2010-4-15 3:15:1
   27       8000  1000ac1a000          2  MSGOBJ_GetMem:583      2010-4-15 3:13:18
   28       8000  1000c1e2000          2  MSGOBJ_GetMem:583      2010-4-22 2:28:22
   29       8000  1000c562000          2  MSGOBJ_GetMem:583      2010-4-15 3:16:54
   30       8000  1000e580000          2  MSGOBJ_GetMem:583      2010-4-15 3:18:6
   31       8000  1000ec88000          2  MSGOBJ_GetMem:583      2010-4-22 2:28:22
   32       8000  1000ffee000          2  MSGOBJ_GetMem:583      2010-4-15 3:10:4
   33        122  1001042b300          2  MSGOBJ_Create:59       2010-4-15 3:37:27
   34        122  1001042b780          2  MSGOBJ_Create:59       2010-4-15 3:37:27
   35        122  1001042b980          2  MSGOBJ_Create:59       2010-4-15 3:37:26
A module triggers the MSGOBJ_Create function to release memory but fails. Finally alarms are generated, indicating that the memory usage exceeds the threshold or the memory leaks.
Alarm Information
None
Handling Process
Step 1  Collect the logs and send them to Huawei R&D engineers for analysis.
Run the log collection tool to collect the logs.
Enter the MML mode and run the mem 1002 command to check whether memory leakage of the TLV message module occurs.
Send the displayed messages to Huawei R&D engineers.
Step 2  Based on the analysis result, Huawei R&D engineers give solutions to upgrade the S2600 version.
Root Cause
If the previous phenomena occurs, check whether special applications or pressure tests are being implemented, and then check whether memory release failures exist in logs.
1. Check whether a large number of I/O requests are received before the alarms occur.
Step 1  Consult with onsite engineers.
Step 2  View the events generated on the S2600.
2. Locate the memory leakage of the TLV message module.
Step 1  Perform a random operation.
Step 2  Enter the MML mode, run the mem 1002 command to view the displayed messages, as shown in the following:
Index  Size(Byte) Address(HEX)            Type  Function(Line)            Time
    1        122  10015bd9b80          2  MSGOBJ_Create:59       1990-4-4 7:21:40
    2       8000  1001f384000          2  MSG_WaitQueu..t:115    1990-4-4 7:19:42
The message in blue is a normal request of memory release while the message in red is not. Of the message in red, the MSGOBJ_Create: function under function (Line) indicates the memory that is not released. (In this example, the memory in the DFT module fails to be released). Find the relevant messages by querying their times to determine the memory release application process. And a memory leakage error is found in system code.
Suggestions
Note that alarms on the S2600 R2 are not automatically cleared after the corresponding faults are rectified. An alarm indicator is turned off only after the alarm is manually cleared.

END